Posts

Post not yet marked as solved
1 Replies
312 Views
Hi. We have 2 apps in the store with universal links working fine, and we are readying the launch of a new version, essentially the same codebase but with different branding and into a different territory. however with this one universal links are not currently working. When the app is installed, swcutil shows the following: App ID: [REDACTED] App Version: 331.0 App PI: <LSPersistentIdentifier 0x5ccc0ee20> { v = 0, t = 0x8, u = 0x6b8, db = E038B2E7-CA87-4BA2-A129-C25394D0F72F, {length = 8, bytes = 0xb806000000000000} } Domain: [REDACTED] User Approval: unspecified Site/Fmwk Approval: denied Flags: Last Checked: 2024-02-16 12:06:39 +0000 Next Check: 2024-02-21 11:08:37 +0000 suggesting the CDN was denied access, but if I query the CDN using https://app-site-association.cdn-apple.com/a/v1/DOMAIN I get the correct app-association contents back. with the previous apps, they were well established before we introduced universal links, but this one is not yet available on the store. the debug build pointing at production seems to work (not using mode=developer) but the TestFlight build does not. we are confident in the contents of the app-association file as it mirrors the other apps. It's been suggested that this could be because the app is not yet available in the store. Is this the case?
Posted
by JW-SDG.
Last updated
.
Post not yet marked as solved
1 Replies
2.2k Views
Since iOS 13.4 (or 13.4.1) we have started seeing an issue in our hybrid app where if the user is on a slow network and they tap back before all resources have finished loading (by this i mean the page itself has finished loading but other assets and JS files have not finished loading) then an error is thrown: Error Domain=NSURLErrorDomain Code=-999 "(null)" UserInfo={NSErrorFailingURLStringKey=https://www.website.com, NSErrorFailingURLKey=https://www.website.com, _WKRecoveryAttempterErrorKey=&lt;WKReloadFrameErrorRecoveryAttempter: 0x2839b46a0&gt;} sometimes, it's thrown twice. if the page in the error is the one the user is navigating away from, then the page they are going back to will continue to load. However if the single error, or the second error (if two are thrown) contain the page begin returned to, loading stops and the page never refreshes. Im at loss to explain this and the only solution coming to mind is to retry if the page is not loading, though im not keen on this. It doesn't seem to happen on versions lower than 13.4 Thanks
Posted
by JW-SDG.
Last updated
.