what android permissions required for deep link in versions 12 and 13 - android-12

deep links URls are not working for android 12 and 13 working expected upto 11 version devices.
I did autoverify= true in intent and signature is matching with the the website wellknown folder. what permissions should use for deep link work in android 12 and 13. and is it true that in android 12 deep link works in production mode after match the signature.

Related

bluetooth LE startscan not showing scan results on certain API levels

I finally got some scanning set up on Android Studio and ran the code, but it did not work on my phone (API level 21). I tried with another phone at API level 28 and it still didn't show any scan results. Finally, I used an API level 30 phone, and it worked.
The code that I have is from this article but even when I tested the author's source code, I had the same result: didn't work on API level 21, 29 and worked on 30.
The source code is made to work with API level 21 and up. So is this an issue in the phone's settings for Bluetooth? I am really confused since at least the source code should have it working with API 21+.
On both of those phones that scan results were not showing, I have tested other commercial BLE apps and all worked on the API 28 phone but almost none on my API 21 phone. The few that did work on my API 21 phone were high-production level apps like Dabble.io and ArduinoBlue.
Perhaps for older android versions, there may be some additional tweaking to do besides your usual: bleScanner.startScan()

WKWebView on iOS 14 only loads content after a significant delay

There seems to be some issue with loading content in WKWebViews in iOS 14. Whenever something is loaded (either a webpage or html string) it takes 25 seconds before the loading actually starts.
I've tried this with a production project and a couple boilerplate WKWebView projects written in Swift and Objective-C, all of them have the same 25 second delay.
This happens in the simulator for both iPhone and iPad on two Macs, both running Catalina and Xcode 12 beta 3.
I haven't tried this on an actual device yet as my primary phone is the only device I have that is capable of running iOS 14 and I prefer not to install iOS 14 on it just to check if this issue is present.
Has anyone else seen this issue?
After two nights working on this thinking it was a mistake I made in SwiftUI (WKWebView inside UIViewRepresentable), I came to the conclusion that this is an issue with iOS 14, but only on the simulator. Not fixed in Xcode 12 beta 4.
There is no delay in iOS 13 on the simulator. You can easily test this by opening Safari in a simulator running iOS 13 and in a second simulator running iOS 14. Any webpage in Safari iOS 13 will open almost instantly. Any webpage in Safari iOS 14 will open with a delay of 20-30 seconds (unless it is a link you click on the website itself).
There is also no delay if you open a webpage in WKWebView or Safari on a real device with iOS 14 (tested with iOS 14 beta 4).
I reported this issue to Apple via the Feedback Assistent app.
[UPDATE] Seems fixed in Xcode 12 beta 5: no longer a delay in the simulator.

Android Gradle Build is taking extreamly long for no reason

When I build or sync gradle in Android studio it takes a very long time and I'm not really sure why it happens, I tried uninstalling and deleting all files then installing again and is still happening, it happens in all projects, I even reinstalled and started a new project with only the "hello world" text view and it took around 13 minutes to compile.
I don't know if these images help, this is the build with the hello world project. if you need any other information, tell me where to look for it and ill post it PLEASE HELP.
EDIT:
I updated Android Studio and built again and I got the following information; these processes are taking the most time:
:app:transformClassesWithInstantRunVerifierForDebug 3 m 19 s 175 ms
:app:transformClassesWithInstantRunForDebug 3 m 30 s 967 ms
:app:transformClassesWithDexBuilderForDebug 15 m 31 s 159 ms
:app:transformDexWithInstantRunSlicesApkForDebug 1 m 6 s 762 ms
I hope this helps
It could be because of your internet connectivity. If you don't have good internet connectivity try enabling "Offline work" under android studio settings.
Build,Execution, Deployment ->Build Tools ->Gradle.
You batter use offline gradle.
Use local gradle destribution
Check Offline work

iOS 12 beta 4 CoreLocation from background launch

My app tracks users' travel (with their knowledge and consent, and with appropriate permissions set). A significant location change event starts the app, and then the app starts updating locations.
This works great for iOS 10 and 11, but it isn't working for the iOS 12 betas (tested beta 3 and 4) - the app is getting started, but it is either not getting location updates, or it is not staying active in the background.
I filed a bug report with Apple, and they called my bug report a dupe of an existing bug that's open, but I couldn't see details on the existing bug.
Does anyone have any more information on this? I scoured release notes and developer event presentations, but I didn't find any mention of something Apple purposefully changed that might cause this.
What I'd really like to know is if there's an intended behavior change that I need to support before the final iOS 12 release. Even better, if there's some workaround that will get this working in the beta versions, that would let me sleep at night...
Seems to be fixed in iOS 12 beta 5 or 6 - upgraded iOS and it started working without other changes.

Android Studio 2.2.3 - minSdk(API21) > deviceSdk(API17) [duplicate]

This question already has an answer here:
Mac OSX - minSdk(API 18) > deviceSdk(API 15)
(1 answer)
Closed 5 years ago.
I get this error when I try to run an android tablet as an emulator. Does it mean my device is older than the Android Studio version ?
Exactly, it means you are developing an app that requires API 21 or bigger to run, and your device has API 17. Open your Project Settings and change min requirements to 17 and see if it runs. If you're not using some special control, object or method, maybe you will be successful on this, and will get your app requiring API 17 as minimal base to run. Case negative, you will have to investigate where the problem lives, may be a property, object or method. Luck.

Resources