-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build errors in .NET 8 for iOS related to PPRiskMagnes package #27
Comments
I am experiencing the same issue. I tested it using the sample project and encountered the same problem, which seems to be related to PPRiskMagnes. As a result, I am unable to build the iOS project. |
@mickbyrne, have you found any workaround? |
@wayousuf no, not as yet. I think we're going to have to just fork these bindings or do them all ourselves. |
Great to hear that the libraries are in use. I am no longer having time to check and/or do the upgrade. Feel free to fork/update then create PR. We all contribute to the community. Regards. |
@tuyen-vuduc thanks for the update. We understand how time consuming this kind of work can be. Thanks for all your efforts over the years on this SDK (and Mapbox!) |
@wayousuf (and may be of interest to @tuyen-vuduc), we were eventually able to get this working by adding a bunch of additional properties in the .csproj file to ensure a number of the dependencies were linked properly. First, to fix the problem with the PPRiskMagnes package, in the top-level
Then to get the KountDataCollector package we added the following
Good luck! |
@mickbyrne That's a great insight. Might you try removing/adding to find out if only the flag is needed? |
@tuyen-vuduc we tried a bunch of things already. Everything in those snippets is required to get it to work. |
These conditions used to work well. It looks like
|
I'm getting build errors when using these .NET 8 Braintree bindings which appear to be related to the
PPRiskMagnes
framework. During the build, there's a warning that reads:This is immediately followed by this error:
PS We love your work here, keep it up!
The text was updated successfully, but these errors were encountered: