-
Notifications
You must be signed in to change notification settings - Fork 23
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
Proper macOS support for API identities #542
Comments
In a fork, I tried manually overriding the platform values defined in The errors go away if I make it pretend to be iOS - doesn't work even with the macCatalyst values. I may have to keep using this fork as a workaround in the meantime. |
Hi, @megastep |
This issue is stale because it has been open 7 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue was closed because it has been stalled for 5 days with no activity. |
was there any resolution on this? |
Hello, @megastep . The solution you provided above will work for now, even though it’s not ideal. The issue is that you need to ensure this change isn’t lost after the pod install. As for a proper solution, I’ve passed the task to the team to fix the problem. I can’t say exactly when it will be ready, but I will definitely get back to you with an update as soon as we release the fix. |
I am using my patched fork with the Swift Package Manager so no worries for now. I'd love to know when I can safely switch back to the mainstream package though... |
I have several universal iOS / macOS apps (not Catalyst - separate apps with a common code base). When running the macOS version, I get a bunch of these errors in the console:
I believe the SDK sends the "macOS" platform to the API, which in turn returns this failure. This creates downstream issues as I think it prevents my users from being identified properly and re-associated with their other accounts.
It sounds like an easy fix would be to simply allow the backend to recognize macOS platform values, as otherwise all of the SDK compiles and is functional, and can process purchases, etc.
The text was updated successfully, but these errors were encountered: