I noticed that the AASA file is not downloaded (by monitoring the API calls in Charles) on iOS 13.1.
I was going through the WWDC https://developer.apple.com/videos/play/wwdc2019/717/ video, but could not find any hint whether we need an additional step on iOS 13.
Anyone experienced the same problem?
It works on iOS 12.2 and earlier.
i was facing this same issue. I found that was charles root certificate the cause of the AASA file not being downloaded. After I removed it from my device, AASA file was downloaded again and universal links worked fine.
You can check in your console for error if any during file download on first installation
https://ios13.dev/universal-links-debugging-on-ios-13-cjwsux93w001p6ws1swtstmzc
And if you want to validate JSON format
https://branch.io/resources/aasa-validator/
Related
I have been trying to upload an iOS app to Appstore but its only appearing on "Activity" tab for 3-5 minutes and then disappears.
Then I got an email from Apple saying that my app is rejected because it is using UIWebView in one of the view controller. I deleted that particular screen and reuploaded the app and had the same error email.
Then I checked my third-party sdks like FacebookLoginSDK and GoogleSignInSDK and updated those and then checked that if the app has no UIWebView which it did not. Then i reuploaded the app but this time again I had the same error email. I have searched the whole storyboard source code and the whole app code to look that if there is any sign for UIWebView but there is nothing, but still I am getting this email.
I also tried deleting 'Derived Data' folder several times and cleaning the build folder also but nothing helps.
On the other hand I have uploaded a different app today which had UIWebView and it got approved but I also got the same email for not using UIWebView.
Does anybody had this kind of experience or can anybody tell me whats going on ?
I got the same issue before.
If you have uploaded the build and showing it in activity tab for few minutes then its not mean that issue is only about UIWebview but there can be some other issue as well.
I have uploaded my app n got the mail related to UIWebview, so I coverted the UIWebview to WKWebView and again I uploaded but that time same thing happend.
I failed to tackle the problem.
Then I mailed to Apple Developer Support and they replied like
Any of the third party library internally using some privacy data you should ask permission for the same.
Then I checked Info.plist, I have given each permission in list still how it comes that we don't understand.
Finally then after whole search the one third party library internally using motion related data without permission so this happened.
Then I have added that in plist and then again uploaded and its approved.
So please you can check your info.plist and also check whether your third party library using any privacy sensitive data without permission or not.
May it help you at some point.
Make sure you update all your plugins to the latest version!
Check this: https://ionicframework.com/blog/understanding-itms-90809-uiwebview-api-deprecation where you can find the plugins that have known issues concerning the old WebView usage.
But be aware that uninstalling and re-installing some plugins will NOT will not install the latest available version of the plugin!
So to be sure that you are re-installing the latest version of a plugin, go to the github repository of the cordova plugin and search for the plugin.xml file and open it. Then, copy the version string found in the root xml element.
Finally, install the plugin like that: ionic cordova plugin add plugin_name#copied_version
<?xml version='1.0' encoding='utf-8'?>
<plugin id="cordova-plugin-firebase" version="2.0.5"
xmlns="http://apache.org/cordova/ns/plugins/1.0"
xmlns:android="http://schemas.android.com/apk/res/android">
<name>Google Firebase Plugin</name>
...
...
...
</plugin>
Are you using the AdMob plugin?
It is not enough to check for the absence of "UIWebView" strings!
You have to make sure that all third party plugins are up to date.
One of the trickiest situations I had went to is when I had tried to update an app (using AdMob) on the AppStore after Apple started rejecting apps using the UIWebView.
The generated iOS source code has no UIWebView references, but still rejected!
After a long headache, I realized that the Google AdMob SDK version I'm using is out of date, knowing that I had updated the AdMob plugin from the CLI, but it seems that the SDK is not updated when updating from the npm.
Finally, I had downloaded the latest AdMob SDK from this link https://developers.google.com/admob/ios/download and replaced it in the source code of the AdMob SDK plugin. Then I had followed the instructions found in this link https://developers.google.com/admob/ios/quick-start to update the code in the xCode.
recently a problem appeared in my iOS application. I'm using Shared Web Credential to get associated user credentials:
SecRequestSharedWebCredential(0, 0, ^(CFArrayRef lpCredential, CFErrorRef lpError) {
// stuff
});
It was working fine until recently, when I discovered it stopped working on iOS 10 devices (possibly only 10.2 devices but I don't have older versions to check). Everything should be in order (entitlements, signed apple-app-site-association file on the server) as it works on iOS 9 and 8. Also it works on every version in simulator (even 10.2).
But on real devices iOS 10 it doesn't work. Completion block is called with error code
-25293 (Authorization/Authentication failed.)
"www.webcredentialsurl.com" failed to approve "AppPrefix.AppID"
Does anybody have any idea what might be causing this? Did Apple change something recently? I'm using Xcode 8.2.
Okay, so I finally found out what was wrong. Since iOS 9.3, Safari searches for apple-app-site-association file in /.well-known directory. If there is no such page or it doesn't find this file, it goes to root directory. However, since iOS 10 it goes to root only if page is not found! If you have redirect there, it treats it as if apple-app-site-association doesn't exist. So you either need to remove redirect for /.well-known or put your apple-app-site-association file there.
Official Apple documentation (they updated it recently to inform about /.well-known more prominently. When I was looking for a solution it was only partially mentioned in brackets...)
https://developer.apple.com/library/content/documentation/General/Conceptual/AppSearch/UniversalLinks.html
I have tried to upload app using Application Loader on Mac.
An upload is succeed however there is not any app in iTunes Connect in my app.
Version and SkuID and AppleID is match between app information in iTunes Connect and the app which is uploaded using Application Loader.
so causing of that, I cannot complete 'submit for review'.
Could you help me please?
Thank you for any further help.
succeed upload app
there is not appearance
Binary on iTunes connect is corrupted. To resolve this, check your binary is compatible with Ios 10.
Please use this link for permission in plist file then try to upload new build with new build version.
iOS 10 - Changes in asking permissions of Camera, microphone and Photo Library causing application to crash
https://i.stack.imgur.com/aY8RG.png
If it's not resolved , please contact iTunes connect support to find out the exact reason. They will reply on mailbox with exact reason of binary corruption. Then needful actions to resolve issue.
https://www.apple.com/itunes/go/itunesconnect/contactus
The problem was to use XCode 5.1.
When I use XCode 6.2, everything went thought well.
Use Application Loader with XCode after 6.
Thank you for everyone.
I am getting below error from last 24 hours during IPA upload through Diawi distribution web site -
An error occurred: This request requires an access token, but none was
provided (#400)
Please refer attach screenshot. I have tried with some old IPA which works with Diawi few days ago but same error
Thanks in advance for your help.
This same problem i was faced in mozila firefox. Its works fine in google chrome try with chrome for uploading. Once its done, its alerts the uploading is done successfully.
You have to load this page completely and its showing you process of loading in upper side of page. once this loading done its showing you upload ipa option in uploading area.
If you find issues and want some alternative then, these two would be great options, Even it will give you permission to upload IPA greater than 100 mb.
1) SendOTA.com
2) DeployNinja.com
3) InstallonAir.com
Working now.
I had the same issue. I switch to "SAFARI" browser. And it works.
Please try safari browser.
Try changing your browser or Clear cache and cookies of current browser and you will be able to upload the app to Diawi.
You should check that you select generic type at time of build or if you are using ipa then regenerate it. it happen some time
Try changing your browser to safari or Clear cache and cookies of current browser and you will be able to upload the app to Diawi.
for this problem you can use "incognito mode" (google chrome, SHIFT+CMD+N).
There might be an issue with the way XCode 9 is building the app. Instead of using the IPA file do the following:
Set the active scheme to generic iOS Device
Clean the project (Product->Clean)
Build (Product->Build)
In project manager, find the '.app' file. Right click and 'show in Finder'
Right click on the file in Finder and compress it to make a zip file
Drag the zip file into Diawi to create your build
This same problem i was faced in chrome. Its works fine in Safari try with Safari for uploading.
I have an iPad app that we are distributing over the air for QA and Beta testers; we have both a debug and and a release config that we are building. Our build process puts together the website and the PLIST manifest file that that iOS needs to install the app. The release build downloads correctly, but the debug build does not. The only difference between the two manifest files is the application that it's pointing to. I've checked server permissions, signing issues (the same app that won't install OTA can be pushed via iTunes) all to no avail.
Most of the other articles out here deal with the file nearly installing and then choking (that's typically the wrong provisioning file).
Thanks for any help you can provide.
I've gotten this error before when the device has a version of iOS below the supported version of the application.
Check the url on plist file. Make sure it has correct path with http://
It turns out the problem was two-fold. One of the iPads had too old of iOS, and the other was there was a hidden character in the URL
It's also possible that the bundle ID is incorrect. We have multiple bundle IDs so we used to get them mixed up. In addition the icon URL is incorrect. Had that problem too