Develop Reference

Cant open Flutter app after build to release

So I just spend the whole night messing up and reinstalling android studio and vscode and flutter cause I was trying to build an apk for my app that's ready enough to pass out to some friends for testing. when my phone is connected to my computer I can debug my app no problem so I thought no big deal lets push out an apk and show off my work. What a nightmare this has been and still is.
I followed this step by step guide to building an android app... https://docs.flutter.dev/deployment/android
So once I finally got all the mystery errors out enough for it to build an apk I copied the file over to my phone and installed it. Well soon as it installed and still on the pop up I see 2 buttons, Close and Open, only open is greyed out. I cant open my app up.
I tried changing the targetSdkVersion down to my phones android version.I tried building out every possible version and appbundle and apk for all the processors and I just cant seem to get a variant to open. I have the key.properties file all linked up, I used the keytool like in the guide.
Has anyone else build out flutter app but cant open it? I'm stumped... The first few attempts I was getting extra popups for googles play protect so I went and turned off that feature. Ive had my phone in developer mode for years now so I know unknown sources are allowed.
It installs fine, but doesnt create an icon anywhere to be used. Once i exit out of the original install popup the only way Id know it was on my device is to go into settings/apps and find it there, and in there the only options are uninstall and force stop which is also greyed out. So the app is unuseable

How to debug Standalone expo App in android device

I am quite new to react/Expo, I have built an android bundle with expo build:android
now the APK I got is in production mode hence I can not debug it in my chrome dev tool. The problem is I am getting an issue in standalone build only while the development feature was working fine.
Is there any way I can build an expo app in development mode?

AS It has been five months AND there is no reply, I would like to share the approach that I took for this issue.
In the expo, you can switch on/off production mode, in production mode, you can debug and log there this would be the same app running after the standalone build, I think 99% problems would be fixed by this. In some special cases like (for example- notification key, Keystore files) you will have to look for their particular support pages. Let me know if anyone facing still facing issues after the above steps I would surely try to help.

How to use Chrome debugging on a signed Cordova app?

I have been using the Chrome remote device inspector to debug my Cordova app. The debug version of my app has been working fine without errors. However, now I made a signed APK for the first time, which installs and opens up, but hangs in a loading screen when try to use the login functionality in my app.
I believe this could be caused by some error in a plugin, or perhaps Google Maps Javascript API failing to load, but I cannot find out what it is because the Chrome debugging is disabled in a signed app. Is there any way I can turn on the debugging?

It turns out you can turn on debugging by adding android:debuggable="true" in AndroidManifest in manifest and application tags.

Cordova signed apk installs on device but only produces a blank screen

I built an android application and signed the apk following all the steps on this tutorial. Even though the APK builds successfully after installing it on a mobile device it fails to load. I only get a white blank screen. I've searched for solutions and tried most of the suggestions but with no luck.
I then decided to start the project from scratch and guess what? the problem still persists. What could I have possible done wrong? I don't really know where to look because I don't even get an error message.
Please help???

I would try debugging that with a tool like GapDebug (https://www.genuitec.com/products/gapdebug/). I would:
Download and install GapDebug.
Attach your device to your PC/Mac via a USB cable.
Deploy your APK to the device and run it.
In GapDebug, choose your app as the app you want to debug.
At this point you may already see one or more errors showing up in the GapDebug console. If not,
On the device, restart the app.
Check the GapDebug console for errors.

Xamarin Signed Release apk will install but not run

I've been developing an app for a while and now I want to hand it out to friends for testing. The app works perfectly when debugging to my device but when I build and sign the apk and move it to my device I can install it without any errors but it will not run (I don't even get any error messages). Sometimes the screen goes black as if the app is about to start but then it just reverts back to the previous screen (One time the Monogame splash screen appeared before it reverted to the previous screen).
Here is what I have done so far and any specific details:
I'm using Visual Studio Professional 2014 with Xamarin.Android 4.20.
I'm creating my app using MonoGame.
I have cleaned and built my app in Release mode.
These are my packaging options:
These are my linker options:
(I believe choosing "None" only means my apk will be larger).
I created a keystore using Java's keytool.
I created and signed the apk using Xamarin's Visual Studio "Publish" command.
After all of this the apk will still not run.

So it turns out this was nothing to do with the signing or building of the release mode apk, it was actually down to an exception which was only being thrown when the app was built in release mode (I have no idea why this was the case).
The thing that was throwing the exception was the DotNetZip library, I'd post an issue on it's page but it looks like the project is dead anyway (Also, they don't explicitly support Xamarin Android).
My solution was to use ZipStorer alongside Mono's .Net compression implementation. Everything works nicely now.