The full error is
### Rejecting URL 'https://sympliact.com/apple-app-site-association' for auth method 'NSURLAuthenticationMethodServerTrust': -6754/0xFFFFE59E kAuthenticationErr
I am passing the SSL test at https://www.digicert.com/help/ and the AASA validation test here https://branch.io/resources/aasa-validator/. As of the time of this writing the site for Apple's official tool here https://search.developer.apple.com/appsearch-validation-tool/ is down so I unfortunately can't check here.
Does anybody have any ideas as to why I am still getting this error? I have tried uninstalling and reinstalling the app and running the scheme as Release instead of Debug. Perhaps you know of other means of helping me debug the issue?
Related
I am trying to deploy to Hololens 2. I followed all of the documentation located here for deploying from USB, but when I go to Debug .> Start without Debugging, I get the following error message:
Unable to activate Windows Store app. 'Template3D__pzq3xp76mxafg!App'.
The activation request failed with error 'Access is Denied'.
Has anyone else gotten this error before? How did you solve it? There doesn't seem to be any documentation anywhere.
The error message may be caused by various different reasons. And for now, we guess that the issue may happens when VS is trying to activate another app with the same package name on your HoloLens. So, we think the following steps worth trying for you.
Uninstall the existing app with the same name on your HoloLens.
Rebuild your Unity project to another empty folder, then open the UWP project with VS.
Update the DisplayName and Package name property in the Package.appxmainfest file with another name.
In my case, uninstalling the app and deleting the existing build folder didn't help. The solution was very simple: You need to be signed in on the Hololens 2 and keep it on your head. I'm using a PIN for my account and also paired the Hololens and allowed the developer options. I just tried several times to confirm and without logging in, I get exactly the described error. I'm deploying over USB.
The title error is what gets emailed after uploading the ipa via the application loader and below is the error that occurs in debug mode:
ERROR: "The framework
APPNAME.app/Frameworks/PersonalizedAdConsent.framework does not
contain a binary named PersonalizedAdConsent"
I've been getting this error in debug mode when trying to build the project. However, when I build it in Ad-Hoc mode, it builds fine and uploads on the application loader without any issues but then I get the following mail
"This bundle is invalid - The Info.plist file for
PersonalizedAdConsent.framework is missing or could not be read."
I've looked in the Info.plist file as well as .csproj file for this reference and I cannot find it anywhere.
Also searched online, can't find much about the PersonalizedAdConsent.
Any ideas?
So it seems like the issue was because of the following packages:
Xamarin.Google.iOS.MobileAds
&
Xamarin.Firebase.Ads
As far as I can tell, the app needs permissions to request consent to display ads or personalized ads (not too sure exactly) and it build correctly after removing these packages.
These were in a build that I've done on Windows for a different app which did not actually use them but VS for MAC gave me the issues and it turned out to be these packages that were causing it.
Hope it helps!
Unless I enable debugging (Esc > Cmd+D > Debug JS Remotely) then I see this error:
Module AppRegistry is not a registered callable module
This also means that I'm unable to view the bundled app on device. If I try to view the app on device, but still use the dev server (remembering to use an IP address in AppDelegate.m instead of localhost) then I instead get this error:
WebSocket connection failed with error Error Domain=NSPOSIXErrorDomain Code=61 "Connection refused"
even though I've verified that I can open the dev server URL in a browser on the device.
I'm not an iOS developer, so maybe this is really obvious, but how do I go about debugging why these errors are happening, or just not having these errors in the first place?
One reason could be App Transport Security that was added in iOS 9. Please see https://facebook.github.io/react-native/docs/running-on-device-ios.html#app-transport-security for reference. You have to add the NSAllowsArbitraryLoads entry to your Info.plist yourself if you didn't use the React Native CLI to generate your project.
Although this doesn't really answer the 'How do I debug these kinds of generic errors' question, I've found out that in my case the problem was that I created my app using an older version of RN (maybe 0.26?) that had a bug in the scaffolding code it creates (which I stupidly ignored at the time when I found i could work around it by enabling debugging) and updating to newer versions of the app hasn't fixed the issue because that doesn't cause the scaffolding to be updated. By creating a fresh app under RN 0.29, and copying my code into it, everything is now working as expected.
It seems that most of Appcelerator's subdomains are having SSL issues, causing an issue in Titanium's iOS build process.
Does anyone also have this issue?
If so, is there a workaround to get the build process working.
I tried cleaning the project, explicitly trusting their invalid certificate, and disconnecting from the internet during build (produced different results but still failed).
Ex. https://security.appcelerator.com
https://www.ssllabs.com/ssltest/analyze.html?d=security.appcelerator.com
you are not alone, I am also seeing it and so are others...I also do nto think there is a workaround at this point
Appcelerator's response:
https://twitter.com/appcelerator/status/735908332054151170
So I am attempting to build an adHoc version of my app for iOS to test on. However about a minute into the build I get an error
"An error occured while building the application. Verify your build assets are correct"
Not sure what this means, how what asset is apparently missing. I've walked through the entire guide to do it that appMobi provides. I have verified all my assets are in place to the best of my knowledge, and yet it fails. Whats worse is appHub indicates iOS builds are green to build.. and even worse is I can build an Android apk off the same bundle without fail.
I found out my answer to this a long while back. I should have answered it to help keep others informed. The problem ended up being that I was using the wrong certs, unfortunately there was no distinct way to find that out. It took the appMobi/phonegap staff looking into it from the back end to find out that the cert was the wrong type. But in the end I got myself the right certificate, and plugged it in, and it built just fine