If someone encounters this issue and nothing seems to help, take a look at Logcat. In my case, the problem wasn’t in the package that Flutter logs were pointing to at all. It was resolved by adding the proper ProGuard rules.