-
Notifications
You must be signed in to change notification settings - Fork 65
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
Crash in ApptentiveViewActivity.onSaveInstanceState #189
Comments
Hey @TheDoorNextBoy, Sorry for the issue: we'll take a look at it asap. |
@TheDoorNextBoy thanks for the report! We're digging in. In the meantime, could you email us at [email protected] with which the account you're working on? I'd like to keep your Customer Success Manager in the loop so they can help coordinate, if need be. Thanks again. |
Hey @TheDoorNextBoy , can you please let me know the steps that lead to this crash? I am trying to reproduce the same scenario in order to debug the real issue. |
@TheDoorNextBoy, did you get the crash log from the crash reporting tool or were you able to reproduce it locally? Do you have any other logs on top of the crash log? |
Hi there, thanks for your fast response! |
I sent a message to [email protected] earlier and got the following back
Could you check that or give me another email address? |
@TheDoorNextBoy very sorry about the issue using [email protected] -- I'm looking into it. Can you email me directly at [email protected]? |
I am also facing the same crash. Using the SDK version 5.4.1
And then after home option pressed App crashes with following logs:
|
Hey @prashantbankar, Could you share the contents of your |
@TheDoorNextBoy could you share the contents of your Thanks! |
|
Thanks @prashantbankar, Do you also have any reproduction steps? |
@weeeBox
then calling I tried the troubleshoot but it didn't help EDIT: the following log was printed though: |
@weeeBox Any update on this? |
@prashantbankar, we're trying to reproduce the issue on our end. We have a fix ready but really want to figure out the underlying cause of the inflating exception. |
@prashantbankar, what Gradle plugin version do you use? |
@weeeBox Gradle Plugin version |
Thanks, @prashantbankar ! We're digging into this. |
@TheDoorNextBoy and @prashantbankar. We've released SDK version 5.4.7 with a fix for this crash. Can you update and let me know if you're still having any issues? Thanks! |
@CaseyApptentive Thanks for your fast response, But I am really disappointed about your "fix".
Just catching everything and finishing can not be a solution. Please let me know if you plan another update. |
@TheDoorNextBoy, we understand your frustration but cannot reproduce the bug on any configuration (Gradle Plugin/Wrapper version, legacy Android Studio, different app themes). We released a fix to prevent devices from crashing and continued investigating. There will be no unexpected behaviour: if the problem persists - the users won't be able to see Love Dialog. |
Hi @weeeBox, Actually our theme could really be an issue. We are using the following androidx libraries:
Our gradle version is gradle-5.4.1 |
Hi @TheDoorNextBoy, we need to create an app with the very same dependencies, Gradle plugin/wrapper versions and styling as your app in order for being able to reproduce the issue. Would you be able to provide these? |
Hi, I do get the following crash report
I assume this can happen when something else crashes in onCreate before addFragmentToAdapter() is called. The generic catch should be removed there to find the real issue. A null check in onSaveInstance state could be a quick fix.
Edit: version is 5.3.1
The text was updated successfully, but these errors were encountered: