-
Notifications
You must be signed in to change notification settings - Fork 50
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
OneSignal Xamarin SDK Version 4 - Now available! #262
Comments
Hi, i have an issue with Xamarin.Forms on iOS. Android is working fine, but on iOS I have this error when building on simulator and real device : I also tested just adding the package to a blank xamarin.forms project and got the same result |
@jeremymarabel Could you let us know the Xamarin version and Visual Studio version you are using? Could you share your blank project where you reproduced the error? |
Hello @jkasten2,
|
Most important is can you please confirm that no "Admob" reference within the dependencies? |
I have the same |
@EmilAlipiev I can confirm no ads references whatsoever in the the list of dependencies for 4.0.0. See the nuspec file here: |
We have reproduce and have a working fix for the |
I am just testing the 4.0.0beta3 but somehow I am not getting any notifications. I dont experience also any crash. I didnt change any single code line only adjusted deprecated part with the new ones. any idea what could be the problem? |
@EmilAlipiev Thanks for trying out the beta, is this issue only happening on Android? |
@skir @jeremymarabel We fixed the XCFramework issue you were seeing in beta1 and 2 in beta3. Try it out and let us know how it goes. |
Testing 4.0.0beta4 using Visual Studio 2022 and a physical iOS device. I do have a notification service extension in the solution. Everything works -- until I add delegates for NotificationWillShow or NotificationWasOpened. Then the app crashes. Debugger just returns a useless null exception error back up to Main. Oh, and the extension doesn't appear to ever be called. I was having this problem with 3.x though too. |
Is ios still using admob on 4.00beta4? I get this error on simulator and this issue is normally caused by admob which i dont use directly but only Onesignal |
There's no AdMob dependency in any OneSignal SDK. Can you please file a bug with the specific issue you're seeing, if you think it may be related to our SDK? |
Gravedad Código Descripción Proyecto Archivo Línea Estado suprimido al exportarlo para instalarlo al teléfono real manda ese error |
alguien sabe como solucionarlo |
your link step-by-step-xamarin-3x-to-400-upgrade-guide is broken, i am not able to follow any guide |
Description
The OneSignal Xamarin major release version 4 is now in Available!
This version includes many exciting changes including an overall simplification of the API as well as many of the underlying native improvements and bug fixes.
Some key changes:
Migration guide
See our Step-by-Step Xamarin 3.x to 4.0.0 Upgrade Guide to get started!
Why you should start migrating now
Most importantly, we want to give you the opportunity to voice your opinion and provide feedback so that we can make changes as needed to better suit your implementation.
Furthermore, it is always beneficial to get a head start on migrating your implementation to ensure a smooth transition. As we continue improving OneSignal, being fully migrated to the latest version of the SDK will help minimize potential issues and ensure you can focus on providing value to your customers, improving your business, and creating a delightful messaging experience.
To begin migrating your app to version 4, read our migration guide here. Regarding this guide, please let us know if anything could be clarified or communicated better.
Releases Page
We are looking forward to hearing from you.
The text was updated successfully, but these errors were encountered: