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
Related
Everytime I try to upload a build to itunes connect I get this error. Otherwise project works well in simulator and on iphone. Any suggestions? I can upload logs, but they're very long. I've tried cleaning, restarting xcode, adding the specific reference to the linked libraries list.
Update: That took a while. I solved it by moving all of my certificates from login to system. I'm not really sure how this helped exactly, but I do know that it fixed the problem.
I had the same problem and same message (just happened with no warning and very little explanation while uploading the archive).
Moving certificates to system did not do it ... but in the process I had to re-issue a distribution certificate and that solved the problem for me.
I had project configuration issue. I placed x86_64 to VALID_ARCHS project setting and Carthage didn't strip simulator architecture. For some reason logs didn't contain any error and I had hard time investigating.
After I deleted x86_64 from VALID_ARCHS it uploaded build without issues.
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?
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.
I have recently updated my Xcode and started having this error.
2014-11-03 15:03:54.222 App[13141:60b] Error loading /private/var/mobile/Applications/677127BD-5230-4D5F-B70E-AF728439D34B/tmp/AppTests.xctest/AppTests: dlopen(/private/var/mobile/Applications/677127BD-5230-4D5F-B70E-AF728439D34B/tmp/AppTests.xctest/AppTests, 262): no suitable image found. Did find:
/private/var/mobile/Applications/677127BD-5230-4D5F-B70E-AF728439D34B/tmp/AppTests.xctest/AppTests: code signature invalid for '/private/var/mobile/Applications/677127BD-5230-4D5F-B70E-AF728439D34B/tmp/AppTests.xctest/AppTests'
DevToolsBundleInjection: Error loading bundle '/private/var/mobile/Applications/677127BD-5230-4D5F-B70E-AF728439D34B/tmp/AppTests.xctest'
I have done my Google search as usual. But I haven't found any solutions yet. Source I have looked and tried to resolve my issue with is,
http://marcschwieterman.com/blog/testing-in-the-sandbox/
When it happens?
It only shows this error if I run uni test on device. On simulator it works as expected. Running application from normal target does not show this error.
When error shows up while running Uni Test app does not crash. It just fails to load xctests.
Anyone having similar issues? and manage to resolve it?
I've encountered exactly the same problem. I was able to fix the problem by setting the provisioning profile to something other than Automatic on both targets (the test and the test host).
I verified this was the problem by reverting it back to automatic, and the problem reoccured.
Xcode 10 here.
For me the issue was the discrepancy between the Project deployment target and the Target deployment target. Once I had them matching, XCTest started working.
#tagy22's comment worked for me
Had this error, I had to set both targets provisioning profile to a wildcard profile.
I found that if I deleted all iOS developer certificates from OS X keychain and the iPhone developer portal, and then let Xcode re-request the development certificates, the problem is resolved.
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