When our App is running in the background and the user creates or deletes an employee via the Clover Employee App, our App crashes and a message appears; "Unfortunately, App Name has stopped.". I am running adb logcat to try and pinpoint the error but thought I would see if others have experienced this issue.
If you could supply the stacktrace of the exception that caused your app to crash from logcat that would help.
OK, so it was the appEvent "refreshmerchantprops" which was triggering the broadcastreceiver for my App and causing the crash. Is there a way that I can identify an App Notification being specifically for my App with intent.getStringExtra(), perhaps app ID? I am currently using both the appEvent and payload for passing data to my application. Are there other clover native notifications that could crash the App? For the time being, I will check to see if payload == null to identify a notification that isn't intended for my App.
3 People are following this question.
