-
Notifications
You must be signed in to change notification settings - Fork 42
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
CleverTap Plugin 1.2.2 NullPointerException #58
Comments
Hey @nafas-natasha , we have fixed this issue on our side in the current v1.2.3. Let us know if you are still facing this issue. Thanks |
Thank you! will try it again. |
Hello, @william-ct sorry to say this but I'm experiencing this null exception again after updating to v.1.3.0. For now, I will rollback to v.1.2.3 until there's a new fix for this. another log of the same error: Here's my flutter doctor: Please help. Thanks! |
Hi @nafas-natasha , we have added a fix for this issue. You can find the commit here. Will be releasing a new version soon. Thanks! |
Hello, I've been using the clevertap plugin for Flutter version 1.2.0 since last year to use Native Display, Push Notification, and In App Message campaign. Then I updated it last month to version 1.2.2. Ever since the update, I have been receiving crash report caused by NullPointerException in CleverTapPlugin.java on my app Firebase Crashlytics dashboard. This never happened before with version 1.2.0.
Here's the crash log detail:
Here's my flutter doctor:
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 2.0.4, on macOS 11.2.1 20D75 darwin-x64, locale en-ID)
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
[✓] Xcode - develop for iOS and macOS
[✓] Chrome - develop for the web
[✓] Android Studio (version 4.1)
[✓] VS Code (version 1.58.1)
[✓] Connected device (2 available)
For now, I decided to roll back to plugin version 1.2.0. I was hoping to use newer version of CleverTap SDK. Please help!
Thank you.
The text was updated successfully, but these errors were encountered: