Posts

Post not yet marked as solved
25 Replies
36k Views
After upgrading to Xcode 12.5 and iOS 14.5, I can no longer debug my app on my local physical device. I get the below error. I searched and cannot find any answers. How do I fixed this? Details Unable to install "MyApp" Domain: com.apple.dt.MobileDeviceErrorDomain Code: -402620375- The code signature version is no longer supported. Domain: com.apple.dt.MobileDeviceErrorDomain Code: -402620375 User Info: {   DVTRadarComponentKey = 261622;   MobileDeviceErrorCode = "(0xE8008029)";   "com.apple.dtdevicekit.stacktrace" = ( 0  DTDeviceKitBase           0x000000011edd83b8 DTDKCreateNSErrorFromAMDErrorCode + 220 1  DTDeviceKitBase           0x000000011ee16ae1 __90-[DTDKMobileDeviceToken installApplicationBundleAtPath:withOptions:andError:withCallback:]_block_invoke + 155 2  DVTFoundation            0x0000000107881b7c DVTInvokeWithStrongOwnership + 71 3  DTDeviceKitBase           0x000000011ee16822 -[DTDKMobileDeviceToken installApplicationBundleAtPath:withOptions:andError:withCallback:] + 1440 4  IDEiOSSupportCore          0x000000011eccf999 __118-[DVTiOSDevice(DVTiPhoneApplicationInstallation) processAppInstallSet:appUninstallSet:installOptions:completionBlock:]_block_invoke.294 + 3534 5  DVTFoundation            0x00000001079b4931 __DVT_CALLING_CLIENT_BLOCK__ + 7 6  DVTFoundation            0x00000001079b655b __DVTDispatchAsync_block_invoke + 1191 7  libdispatch.dylib          0x00007fff20508603 _dispatch_call_block_and_release + 12 8  libdispatch.dylib          0x00007fff205097e6 _dispatch_client_callout + 8 9  libdispatch.dylib          0x00007fff2050f5ca _dispatch_lane_serial_drain + 606 10 libdispatch.dylib          0x00007fff2051008d _dispatch_lane_invoke + 366 11 libdispatch.dylib          0x00007fff20519bed _dispatch_workloop_worker_thread + 811 12 libsystem_pthread.dylib       0x00007fff206b04c0 _pthread_wqthread + 314 13 libsystem_pthread.dylib       0x00007fff206af493 start_wqthread + 15 ); }- System Information macOS Version 11.3 (Build 20E232) Xcode 12.5 (18205) (Build 12E262) Timestamp: 2021-04-29T22:41:18-04:00
Posted Last updated
.
Post not yet marked as solved
20 Replies
2.5k Views
So Apple just announced that iOS 14 ships tomorrow 9/16/2020. However, there are many threads on here showing how App Clip development is broken and there is no way to test the end to end experience. App Clip Development and Testing seems to have been broken since iOS 14 Beta 5 What is going?
Posted Last updated
.
Post marked as solved
13 Replies
5.2k Views
I've watched every video and ready every piece of documentation available on App Clips. I can't seem to figure out how to get the App Clip Card to show. I've added the associated domains entitlement to my app and app clip. I've updated my Webserver to have the proper apple-app-site-association file. I've updated my bundle IDs to enable Associated Domains. I can go direct to the App Clip "App" by debugging, but I can't see the Card that prompts the user. What am I missing? Thanks! Mike
Posted Last updated
.
Post not yet marked as solved
1 Replies
616 Views
Activity in these forums are way slower than I thought they would be. Where is the "hot spot" for active discussions about the Apple development ecosphere?
Posted Last updated
.
Post not yet marked as solved
0 Replies
672 Views
I was able to get my App Clip to show using a Safari Smart Banner and enabling localized experiences in the iOS developer mode on iOS 14 beta 5. The App Clip shows up after I click okay on a Safari Smart Banner that appears on a page that has the Smart Banner meta tag. Clicking “Open” on the App Clip doesn’t do anything. It’s basically grayed out. Is there a way to test a full end to end experience? Is Safari Smart Banner the only way to evoke the App Clip? How do I generate a shareable iOS message? How do I generate a QR code that directly opens the App Clip? Thanks! Bumbleparrot
Posted Last updated
.
Post not yet marked as solved
5 Replies
4.3k Views
I'm trying to call a URL using URLSession to log out of an oauth2 session in swift in an iOS app. The URL is something like this:Notice that some parameters are URL Encoded* https://xxxxxx.auth.us-east-1.amazoncognito.com/logout?client_id=49jaf4a848hakh&logout_uri=myapp%3A%2F%2F&redirect_uri=myapp%3A%2F%2F&response_type=token I get a run time error using this URL in a data task that says:* Error Domain=NSURLErrorDomain Code=-1002 "unsupported URL" UserInfo={NSUnderlyingError=0x60000202ccf0 {Error Domain=kCFErrorDomainCFNetwork Code=-1002 "(null)"}, NSErrorFailingURLStringKey=myapp://, NSErrorFailingURLKey=myapp://, NSLocalizedDescription=unsupported URL} I already have "myapp" in my info.plist.* <array> <dict> <key>CFBundleTypeRole</key> <string>Editor</string> <key>CFBundleURLName</key> <string>com.***.yyy</string> <key>CFBundleURLSchemes</key> <array> <string>myapp</string> </array> </dict> </array> Below is the code to execute this simple URLSession data task* 				let s = URLSession.shared 				let u = URL(string: "https://***.yyy.auth.us-east-1.amazoncognito.com/logout?client_id=7c2aqa0fibv51v8valq6pagtoq&logout_uri=myapp%3A%2F%2F&redirect_uri=myapp%3A%2F%2F&response_type=token")!				 				 				let t = s.dataTask(with: u) { (d: Data?, r: URLResponse?, e:Error?) in 						if e != nil { 								print("error: \(e)") 						} 						let decoded = String(data: d!, encoding: .utf8) 						print("Data: \(decoded)") 						print("url Response: \(r)") 						print("Breakpoint") 				}.resume() I've tried with both URL strings below and still get the same error* let u = URL(string: "https://***.yyy.auth.us-east-1.amazoncognito.com/logout?client_id=7c2aqa0fibv51v8valq6pagtoq&logout_uri=myapp%3A%2F%2F&redirect_uri=myapp%3A%2F%2F&response_type=token")!				 let u = URL(string: "https://***.yyy.auth.us-east-1.amazoncognito.com/logout?client_id=7c2aqa0fibv51v8valq6pagtoq&logout_uri=myapp://&redirect_uri=myapp://&response_type=token")!				 Why doesn't swift like "myapp://" or (myapp%3A%2F%2F) being a query string parameter? Stack Overflow Question - https://stackoverflow.com/questions/63224049/swift-url-with-custom-scheme-in-query-string-fails-redirect-uri
Posted Last updated
.