I built a react-meteor android app, which I signed with Android Studio for a release.
The app is loading with a splash screen and then stuck in den loading screen of my React Komposer ( I guess the subscription does not get ready ).
However running the app via:
meteor run android-device --mobile-server https://fuldacity.de
runs the app successful, as well as running from signed debug apk.
I really do not now where to start to debug this problem. I guess there is a possiblity to get some error logs out of Android Studio? I would be really glad on any inspiration on how to tackle this problem!
Furthermore I have the feeling it is connected to my setup. I have a domain hosted by domainfactory, where I also get my https certificate from. The domain is then redirected to Heroku, where my App is hosted. I furthermore redirect all http:// accesses to https:// via the Meteor package force-ssl.
`
Try like this:
meteor add-platform android
After
meteor install-sdk android
After
meteor run android-device --mobile-server https://fuldacity.de
Long story short the error was on domainfactory where I have choosen the IP instead of the domainname as A configuration for the nameserver.
Domainfactory does not allow a the correct settings for usage of heroku. Now I use the nameservers of Route 53 which could setup the right CNAME settings to heroku.
For the debugging I also learned that you can
meteor run android-device --server https://fuldacity
then go to your chrome browser (on your pc) open the developer tools and there you can find remote devices which gives you all the error outputs from the client side!
This let me to the network error, which only appeared on the mobile devices.
Related
How do I build the react-native app so I can test it in hockeyapp without being connected?
I'm using react-native-hockeyapp and successfully built the app, which listed it on hockeyapp, but now with the hockeyapp changes:
It does not run on a connected device with run-android and I get a white screen and no console debug messages anymore.
When I uploaded the app_Debug.apk to the hockeyapp by dragging it on the website, I got an invite. Run it on my device and get the white screen and the following two errors:
a. unable to load script from assets 'index.android.bundle'. Make sure your bundle is pakcaged correctly...
It then shows a white screen.
b. If I shake and press reload it says: could not connect ot development server. I don't want to connect to development server. I want to test it disconnected!
How do I build the app? In Android Studio? Any pointer to instructions?
And how do I preserve the possibility to react-native run-android so that I can test it locally and debug quickly for development?
I created a keystore and then went to myproject/android folder and gradlew assembleRelease
See https://github.com/benloopcompany/react-native-hockeyapp/issues/84 for more details
I have a beginners question.
I deployed my meteor website on Galaxy. Now I want an android version of my website. I followed every step in mobile docs. Everything is working fine on windows and the app is working as expected in the emulator.
Now if I build my app for production, we need to give a host and port.
What port and host should I use so I can use the same code base as my website?
Here is My domain
I tried:
meteor build ../output --server http://heybuddy.meteorapp.com:80
But without success. Or do I see it totally wrong.
Thank you for any answers!
The host is where your server is accessible, typically the address you use to access the browser-based version of your application / website.
The port is not mandatory.
I'm making a todo list app, using meteor and cordova full code is at: github.
I've added an Android app version. Login is via accounts-password.
The server is running via nodejs with an nginx frontend.
The problem:
If I build the server with the android-platform then connect an android device to it the login buttons appear briefly but then the screen refreshes and they're gone and will not return unless the app cache is cleared.
If I build the server without the android-platform then it works fine. This happens with meteor run android (emulated). meteor run android-device and via loading an APK from the play store.
I assume what is happening is building the server with android platform results in a different version of the code being put on the server which then gets pushed to the phone when it connects.
But I have no clue how to debug this.
I'm building a HTML5 Game and deploying it to my Android phone for testing using Apache Cordova.
Is there anyway to debug my application on the device while it's running, such as seeing the JS Console?
Have you taken a look at the debug.phonegap.com?
Another way you can upload the html to a server or localhost and use it. But this only for outside the apk:
https://developers.google.com/chrome-developer-tools/docs/remote-debugging
You can also run your Cordova project via the AppGyver Steroids tooling, which gives you enhanced access to the Safari and Chrome web inspectors.
I have developed an application using Android SDK 1.5, application works well on Android Simulator.
Now, I am trying to install application on actual device. I don't have the Android device. So, I am going by OTA way.
For this, I have generated the self sign keystore using keytool utility.
And, using Eclipse's "Eclipse Signed Application package.." option I have generated the signed .apk file and moved it to my web server.
Also, i added MIME type on web server for .apk.
But, when I am trying to download and install the same application on device, application get downloaded and it also prompts for permission. After thag when I click on "Install", it fails with error Application Install Unsuccefull.
Interestingly, I test this url on simulator browser, and it worked perfectly well and application get installed successfully.
Even, I checked that, SDCard is there on device. Settings -> Applications and "Unknown sources" option is alos checked.
Am I clear to you all?
Any Idea what may be going wrong here?
Thanks and appreciate your response,
S.Satheesh
What happens if connect the phone via a USB cable and install the application using the adb install command? Testing this will allow you to determine if the problem is with the package or the over the air update.
Also, you could try running adb logcat to view the logs from your phone after the failed install as this should show you what the problem is.