-
Notifications
You must be signed in to change notification settings - Fork 61
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
[question]: Import OneSignal packages unity 6 #769
Comments
Did you manage to solve the issue? Im stuck with the same problem (2022.3.16f1), even tried importing to a new project, but still no luck, OneSignal just doest import its package |
Same problem :( |
I discovered that OneSignal Unity SDK has updated to version 5.1.11 few days ago, and i suspect that something is wrong in this update, something, that blocks us from importing package. Guess nothing left to do than to just simply wait for a new update or try to go back to previous versions with github UPD: tried installing version 5.1.7 from github, worked first try. Apparently, it was for real because of the version 5.1.11 |
@burbaoleg Thank you very much for sharing this information. I am going to try with 5.1.7. I thought my problem was because I did not have the "google-services.json" file in the assets, but since they do not mention it in their documentation, I did not include it. |
Thanks for bringing this to our attention. I've identified that this is currently a bug with our 5.1.11 release. As burbaoleg mentioned, as a workaround:
I've tested this successfully with Unity 6.000.0.29f1.
|
Hi all This issue has been resolved. Importing the package on version 5.1.11 should now work If there are still issues, feel free comment and I'll reopen the issue |
How can we help?
I'm using Unity 6 (version 6000.0.29f1) and attempting to set up the OneSignal SDK (version 5.1.11). However, the "Import OneSignal packages" step fails without providing any error messages or logs to indicate what went wrong. I've attached a video demonstrating the issue.
Has anyone experienced this or have suggestions for resolving it?
Screen.Recording.2024-12-01.at.15.50.59.mov
Code of Conduct
The text was updated successfully, but these errors were encountered: