We recently migrated my apps target SDK to 33, from that app links are not working fine in emulator but not working in real device
I googled about it and manually opted for web address in my device and links are working fine, but I cant ask app users to do that every time
I have read android documentation
https://developer.android.com/training/app-links/verify-android-applinks#manual-verification
Here they mentioned process of manually verifying the domines for the Android above 12
but when I run adb shell am compat enable 175408749 com.myapp.package
terminal is throwing message says
Cannot override 175408749 for com.modere.global because the app's targetSdk (33) is above the change's targetSdk threshold (30)
How can I verify the domain please help me
You can use firebase dynamic link instead of deep link in android target SDK 33
Related
I am trying to use NFC Manager Plugin in my flutter app when I used Lock Nfc Function using these functions:
Handle Tag Function for locking card:
Start session to use handle tag function:
But on some android devices which have Android 13, when we try to use the lock function we face an error :
and we can't turn off The Nfc on the device until about 1 minute, then this error is shown:
also, we try to use the example project on the plugin but it has the same problem.
Flutter Doctor:
we are still on this error trying to fix the issue, any solutions to fix this issue?
I am trying to reverse engineer an app that uses the Android LocationManager. It is attempting to request location updates via the .requestLocationUpdates method. However, I am receiving an error that the network provider doesn't exist:
java.lang.IllegalArgumentException: provider doesn't exist: network
at android.os.Parcel.createException(Parcel.java:2075)
at android.os.Parcel.readException(Parcel.java:2039)
at android.os.Parcel.readException(Parcel.java:1987)
at android.location.ILocationManager$Stub$Proxy.requestLocationUpdates(ILocationManager.java:1151)
at android.location.LocationManager.requestLocationUpdates(LocationManager.java:1019)
at android.location.LocationManager.requestLocationUpdates(LocationManager.java:558)
This error logged after clicking a button in the app and then it crashed. At the time of executing this action, I was using Genymotion Desktop Emulator running a Samsung Galaxy S10 on Android 11.0 API and x86 architecture. After some research, it seems like the issue is due to the fact that Genymotion does not have a network provider enabled. After even more research, it seems emulators can't use the network provider period.
I'm not an Android expert and all of the links aren't exactly the same as my case, so I'm trying to see if there is still a work around/if the outcomes of these links fully apply to me.
Since my issue seems to be Genymotion related, I have decided to try and use Android Studio's emulator instead. I have created a virtual device via the Android Virtual Device Manager (AVD). It is a Nexus 5 API 30 using Android 11.0 (Google Play) on x86 architecture. It is my understanding that there are three location providers in android and the one that I need is the network provider.
My main question is: Do Android Studio Emulators have the network provider enabled?
If not, is it even possible for an emulator to have it enabled or should I consider purchasing a real android phone for this case?
You may be asking why I don't just try to click the same button and see if the error replicates. Well, I simply can't right now. The reason is quite complex, but in short, the button only shows up occasionally for me to press. I don't know when it will be available again, so in the meantime I'm trying to prepare my setup and gain a better understanding of android's location manager.
I have taken over an outdated Android App written in Java
I have progressively upgraded dependencies without issue until I changed the targetSdkVersion from 27 to 30.
This is for a feature that:
Allows user to pick an from the gallery or capture from camera
Saves a value to an application folder
Sends the picture to an API
I know that pre-Android 10, I could add android:requestLegacyExternalStorage="true" in the Manifest file and it would work, but that feature was from Android 10+.
If I downgrade the targetSdkVersion, it works.
Otherwise it throws the following errors:
E/BitmapFactory: Unable to decode stream: java.io.FileNotFoundException: /storage/emulated/0/xxxxx/1380402_672833029402941_703996746_n.jpg: open failed: EACCES (Permission denied)
I have narrowed it down to a permissions issue, due to scoped storage restrictions
I understand the concept behind it but I cannot get it to work.
What do I need to do to fix this in Java code, as I don't know how to apply the examples in Kotlin for Java?
I have tried following some of the answers from below:
Sample app: https://github.com/tinonetic/android-questions-scoped-storages
Write permissions not working - scoped storage Android SDK 30 (aka Android 11)
Scoped Storage android 10.0
Add image to Media Gallery - Android
For one of my project I work with Nearby Connection API with P2P_STAR strategy and I experience issue on discovery with Android 10.
I have tested with Huawei devices that resulted in no connection at all with host and on a freshly updated Xiaomi MI 9t who success to connect but disconnect few seconds after with no exceptions...
Before the update it work well on the Xiaomi.
Furthermore, my app work very well on my android 8 or 9 devices.
I tried to add ACCESS_FINE_LOCATION permission and update Google play services without success...
Our project repository : https://github.com/hbollon/Urbalog
All Nearby stuff is in NetworkHelper class and permissions list is in the constant REQUIRED_PERMISSIONS inside it.
Someone would have any idea?
Thanks in advance
So I have found the issue, on my android 10 devices I haven't activate location and Nearby seems unable to activate it itself...
I never notice that before Android 10 update so is it os related or have I always activated it before? I don't know ^^
However, on the ConnectionsStatusCodes documentation, MISSING_SETTING_LOCATION_MUST_BE_ON status code is marked as deprecated ( https://developers.google.com/android/reference/com/google/android/gms/nearby/connection/ConnectionsStatusCodes ).
So I imagine this is no longer a possible case no?
I got the following log error in my route tracking activity:
06-24 18:50:24.488 7128-7759/com.noureddine_ouertani.www.wocelli50
E/DynamiteModule: Failed to load module descriptor class: Didn't find
class
"com.google.android.gms.dynamite.descriptors.com.google.android.gms.googlecertificates.ModuleDescriptor"
on path: DexPathList[[zip file
"/data/app/com.noureddine_ouertani.www.wocelli50-2/base.apk"],nativeLibraryDirectories=[/vendor/lib64,
/system/lib64]]
After reading some posts and answers (e.g. this or this) about this log error I figured out that it's a known Google Play Services version 9.0.83 issue that causes bugs in some apps that use a GoogleApiClient like mine.
However I didn't test the solution yet. I wanted to downgrade Google Play Services on my Smartphone but Uninstall Updates was greyed out (see Screenshot).
Does anyone know how to do this manually?
By checking the internet for your problem about how to downgrade Google Play Service when the Uninstall Updates was grayed out. I came up with many possible solution. You can check it all and try if this method helps you.
From this Stack Exchnge question, you can try the solution here that states:
If you have the Android Device
manager
app installed then this can also make the force stop/uninstall updates
buttons be disabled.
If you uninstall the Android Device manager app and disable "Android
Device Manager" as a device administrator then those options should be
enabled.
From this forum, the solution here needs you to download and install System App Remover from the Google Play Store. Just check the forum link to know more about the steps and their information.
And lastly, you can also check the solution in the discusion of this forum page.
I solved the problem for my Huawei P8 Lite Android phone like this:
I unlocked my bootloader like in this video
I rooted my phone like in this video
I succesfully checked with Root Checker Basic that my phone is rooted
I downloaded and installed System App Remover from the Google Play Store.
I put my device in Airplane Mode in order to prevent auto upgrade of GPS.
I opened System App Remover and select "System App" from the menu.
After I found Google Play Services in the list which was marked as "Should keep" I selected it and pressed "Uninstall". I ignored the next warning.
Using Settings/Apps, I saw that Google Play Services "Uninstall Updates", and "Disable" Buttons were no longer be grayed out.
I pressed "Uninstall Updates"
Here is the result: Downgrade of Google Play Services to 8.1.18