When building an .apk of my flutter app and installing on my android device the data created is only locally saved not saved online. When using in the android emulator it works perfectly with no errors, even when switching the signing configs to use debug.
There are no firebase rules set, everyone can read and write. There is no fingerprint/sha1 hash set. All android settings have stayed the same since the build version has worked on android correctly.
If there is anything code etc. i can give please ask, not sure what is helpful here as all settings were the same when it was working.
You have not granted internet permission to access the application
Open the AndroidManifest.xml file located at ./android/app/src/main and add the following line:
<manifest xmlns:android="...">
<uses-permission android:name="android.permission.INTERNET"/> <!-- Add this -->
</manifest>
Refer here
Related
i have a flutter app that has firebase and firestore as backend,
it works fine on the emulator when i changed it into apk, but on the real device on the log in page the loading circle get stuck and the app wont proceed the log in procedure.
i don't why does this happen? it works fine as normal flutter on the device but when its apk it only works on emulator.
here is the pic of the laading being stuck
the pic of the mobile
Did you put the internet permission in your androidManifest.xml?
<uses-permission android:name="android.permission.INTERNET" />
The permission is on by default in a debug build, but not in a release build
go to your flutter project and go /android/app/src/main and open AndroidManifest.xml and add this line under the package tag
<uses-permission android:name="android.permission.INTERNET" />
I have created a Flutter app that contains some simple links to emails (mailto:) and external web sites using the url_launcher package.
Do I need to include the android.permission.INTERNET permission for this to work on Android devices?
I have tested on emulators with no issue without the permission but not sure if this would apply to real devices.
Debug mode usually doesn't require any permissions to be added explicitly. But if you will browse through your project files you will be able to see that there are seperate android manifests for debug and release mode of your app. In release mode, you have to add every permission you will be needing explicitly. So yes you have to add Internet permission for packages like url_launcher, google_fonts etc to run in release mode.
I built a game in Unity and I'm trying to export to to Android. I've set the min API in Android player settings to 14. I've confirmed with the AndroidManifest.xml file in both temp/staging and assets/plugins/android that it reflects this. It shows:
<uses-sdk android:minSdkVersion="14" android:targetSdkVersion="17" />
I then exported directly into an APK file right from unity (not through eclipse). I uploaded the APK to the google play store in beta mode. However, when I look at the app screen on the play store I see: Requires Android: 1.6 and up. Why is it doing this?
I'm thinking there might be a problem with the Manifest file but I'm not sure. For example, I'm using AdMob so I have these permissions in the file:
<uses-permission android:name="android.permission.INTERNET"/>
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE"/>
But when I install the app through the beta link it tells me that no extra permissions are necessary. AdMob is working though, I can see the banner ads and the impressions are showing up on my AdMob account. I'm not sure if the no permissions needed thing is related to a bad manifest file or a beta store account. EDIT: Actually if I install the APK manually then it does show the permissions, so I'm guessing it's just a beta thing and my permissions are fine.
To test, I've tried exporting the file as an Android Project, then importing into Eclipse. When I try to do that, it successfully recognizes the project but even though the Finish button isn't greyed out it doesn't do anything...
Decompile your APK file to read AndroidManifest.xml.
Look at this: How to parse the AndroidManifest.xml file inside an .apk package
Apparently this is a known bug, and it doesn't seem to affect published apps, so don't worry about it:
https://gamedev.stackexchange.com/questions/67234/why-does-my-game-display-the-wrong-required-android-version-on-google-play
I'm currently developing an application using PhoneGap in Eclipse. One of the features of the app is that it connects to a remote server through the network. In eclipse, when I run the project as an 'Android Application' directly on the device, everything works perfectly and the device successfully connects to the remote server. This I guess is the 'Debug' build that eclipse offers.
I then go on to create an APK file for the project through PhoneGap's site... I install the APK on the device and when I try to connect, it does not work. The app just hangs when I click on the connect button and does nothing.
I check the debug build and everything works again like a charm. Can someone please tell me what I'm missing ? Do I need to sign the APK file that I'm creating on the PhoneGap site ? Any help would be much appreciated.
Thanks in advance
Maybe you can put
AndroidManifest.xml
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.example.package">
<uses-permission android:name="android.permission.INTERNET"/>
<application>
...
</application>
</manifest>
I need to write Android application which looks for firmware in internet and allows to automatically download selected firmware and perform update on device. Is it possible?
Thanks
It should be possible. I am trying to do the same thing. I posted a question about this as another user. It almost works for me, but my device can't apply the new image on boot time.
Basically you use the RecoverySystem.installPackage(context, packageFile) method to do this. You will also need the following permissions:
<uses-permission android:name="android.permission.REBOOT" />
<uses-permission android:name="android.permission.ACCESS_CACHE_FILESYSTEM" />
<uses-permission android:name="android.permission.DELETE_CACHE_FILES" />
Also, your app must run as a system app. I don't know if you're using the whole Android SDK with Eclipse and the SDK tools, but what I did for that was basically connect my device to my machine and used it for debuggin, then ran the app through the IDE so it gets uploaded and run on the device. And finally use the adb shell command to open up a shell on my device and moved the apk package file from /data/app to /system/app and rebooted.
Check out my post here. It might help you out.
Android development RecoverySystem.installPackage() cannot write to /cache/recovery/command permission denied
You need root, and it won't be automatically applied, but like with cyanogen updater, it reboots to recovery where the user will apply the update by itself
It is possible. Take a look at Clockwork Mod - http://www.clockworkmod.com/rommanager
They have an app which will check for the latest version of the firmware and update it - available on Google Marketplace https://market.android.com/details?id=com.koushikdutta.rommanager&hl=en