App crashes in In-App Messaging card type with empty message body
See original GitHub issue[REQUIRED] Step 2: Describe your environment
- Android Studio version: 3.5.3
- Firebase Component: In-App Messaging
- Component version: 19.0.2
[REQUIRED] Step 3: Describe the problem
Steps to reproduce:
What happened? How can we make the problem occur? This could be a description, log/console output, etc.
Relevant Code:
1. Compose a campaign with Card Type layout
2. Set optional message body to empty
3. App crashes
Issue Analytics
- State:
- Created 4 years ago
- Reactions:5
- Comments:18 (9 by maintainers)
Top Results From Across the Web
Firebase in app messaging app crashing when selecting style ...
enter image description here. Firebase in app messaging app crashing when selecting style and content as card can some one help on the....
Read more >How to Fix All Problem of Message App Not ... - YouTube
Fix Message App Not Working & Not Showing Message Error in Android Phone # Message #Android Facebook ...
Read more >Crashes | Android Developers
There are many situations that can cause a crash in your app. Some reasons are obvious, like checking for a null value or...
Read more >Why Do My Apps Keep Crashing on Android? - Avast
Do your Android apps keep crashing? Discover why and learn how to prevent Android apps crashing and freezing by following these methods.
Read more >Modify behavior of Firebase In-App Messaging messages
On this page · Respond when users interact with in-app messages. Implement a DisplayDelegate to handle Card interactions · Trigger in-app messages ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Since this has started happening recently without any code change in the app, I am suspecting that something has changed on their backend. Their backend is not sending the data to clients in the expected format which is causing this crash. I think there are two parts to this issue:
Hey I appreciate the PR but I’m going to be applying a more general fix to all of our proto parsing to remove this entire class of errors rather than just this one error. I’m going to go ahead and close our your PR but I really appreciate you taking the time to come up with a fix.
I’m also closing out this issue as this is now resolved.