Hi
We have developed the Mini and it is working fine on iOS. However, on Android it does not seem to be loading both on emulator and an actual device. In both, we just see a black screen. I am not able to find any error logs anywhere to find the issue.
Could you provide some guidance about how to proceed with debugging this issue. When I open the Mini with chrome devtools, it loads fine there as well. It is only android on which it is not loading.
Thanks
hi @vaibhav, maybe this finding by another community member could work for you as well.
Thanks for your reply, but I am still a bit lost about how that helps with my issue. I am guessing what the linked post talks about is port forwarding so that any service running on my host machine can be accessed by the android device. However, I do not think that is going to help me, since I do not need access to any local services running on the host. My backend runs on AWS and can be directly accessed by the emulator.
Could you please elaborate on how to use the suggestion in that post for debugging the issue, in case I misunderstood what that post means.
Happy to submit the Mini for review, if your team might want to look at the issue.
in this case, your mini running on the Android simulator can’t connect to your dev server. Minis CLI start a web dev server, and looks like it’s not accessible from your simulator.
That’s why using those commands could help you with your issue.
Thanks. Tried that and unfortunately it didn’t work.
Should mention that when I bootstrapped the Mini using the CLI, that was loading fine on Android. So I didn’t expect it to be a port access issue.
But now that we see a blank screen, there is no way to tell what is going wrong. Is there a way to get some logs which might point to the issue?
Another thing I noticed is that if I debug the app using Chrome Devtools, then the app loads if Chrome device emulator is not on. However if I try to emulate any device size then the mini does not load and we see a loader forever. This might be totally unrelated, but mentioning just in case its not.
Have you tried to connect the Chrome DevTools to the Android simulator to check the console logs?
