I am new to Firebase Test Lab, and I'm having issues running my XCUITests against an iOS app. I have had success running Espresso tests against an Android APK on Test Lab, and have even successfully ran tests against an iOS app that I found on GitHub. (https://github.com/Shashikant86/Scalable-XCUItest) However, it seems that there is something in the app that I'm testing that prevents it from being installed on the Test Lab physical device.
This is not a personal project so the amount of information that I can share is very limited, but I'll share whatever I can from the logs that might be of use without sharing any private information:
HTTP load failed (error code: -1001 [4:-2104])
load failed with error Error Domain=NSURLErrorDomain Code=-1001 "The request timed out."
load failed with error Error Domain=NSURLErrorDomain Code=-1003 "A server with the specified hostname could not be found."
Log from Firebase is in this Gist: https://gist.github.com/ChiWhiteSox56/b6122f4ccd488a3fb0dcfe53aa45e2af
Clearly there's something happening around the app's ability to reach the required server but as I mentioned earlier, I've been able to run the tests successfully against other apps.
Thanks for reading, and if any additional information is required to troubleshoot this issue, I'll try to provide as much as I can.
After joining the Firebase Slack Community and posting this question, I received a twofold response from the FTL (Firebase Test Lab) team.
1) The provisioning profile for the app that I'm testing includes an app group entitlement. App groups are currently unsupported by FTL because they do not have permission to re-sign apps with an app group. Provisioning profiles that may re-sign multiple apps may not have the app group entitlement.
Note: FTL can run tests for apps with an app group entitlement if the app can function without the group. FTL will strip the entitlement, so this does not require any action on the part of the app submitter.
2) As I mentioned above, I was only able to share limited logs from my project. After the FTL team looked into the full logs from my test run, they determined that the issue that I was experiencing was not, in fact, related to the app group issue. It was an unrelated issue, and a bug has been filed to address it.
Related
I'm trying to upload a new build to the app store connect. I usually use my CI for this but since the boss forgot to renew the CI's plan, I need to do it manually from XCode for now. Building and uploading from CI always work so far.
So I've Archived it successfully. But when I tried to Validate or Distribute the app from the Organizer, it failed with the error:
No accounts with App Store Connect access have been found for "TEAM_NAME". App Store Connect access is required for App Store Distribution.
I am using XCode Version 11.6 (11E708), and have already added the account that has App Store Connect access to XCode. The account has the admin role. So far, these are all the fixes that I have tried to no avail:
Restart XCode
Restart Mac
Delete and add the account again
Delete DerivedData
Redownload the certificates and add them to Keychain
Change the signing type to Automatic from Manual, or vice versa
Make sure to disable my VPN
Any combination of the steps above
I have also tried exporting and uploading using xcrun altool --upload-app but it returned these errors:
2021-01-19 22:03:00.239 altool[6155:75984] *** Error: Connection failed! Error Message - The request timed out.
2021-01-19 22:03:00.404 altool[6155:75978] *** Error: Error uploading 'Kolibree.ipa'.
2021-01-19 22:03:00.404 altool[6155:75978] *** Error: code -1011 (Unable to get authorization for username 'USERNAME' and password provided. Authentication failed.)
The network is most certainly working so I don't know why it timed out. Is it from Apple's side? Can anybody help me here? Thanks in advance.
UPDATE: I'm still using Catalina 10.15.4. Does that make any difference? Should I update my macOS?
Okay, after looking it up some more, I found out that the culprit is the ISP. It was blocked by the ISP since I can actually upload when I tethered to my phone. I've also checked the router and it doesn't have any firewall so it's definitely the ISP. Maybe I'll try the steps in #Paulw11's comment in using port 443 to upload now. Thanks.
UPDATE: After more investigation, it is actually much more silly. The ISP injected their ads into the packets that use any port except 443. And that includes uploading the app to the App Store. I tried turning on my VPN and it worked because there's no injection. Thanks again.
For error "Error Finding App Store Connect Credentials", Please go to Xcode>Preferences>Accounts and see if your app store account has been added. In some case when you update the password you need to provide your credentials again here to upload the build to app store.
I archived my app for testing and then tried to export it.
But Xcode asks me to sign the project again, as it doesn't show my previous developer account.
It says :
Apple Developer website is undergoing maintenance
But the website and everything in the developer site seems up and fine!!
Furthermore, I can't believe they have been down for such a long time, it seems there is another problem, because when I try to add the developer account again, it gives me this error:
The operation couldn’t be completed. Unable to log in with account 'xxxxx#me.com'.
An unexpected failure occurred while logging in (Underlying error code 503).
Anyone knows anything about this mystery? Thanks for any help.
The error-message seems to be correct. There is currently a scheduled maintenance.
Source: Apple Developer System Status
I've been working on this app for a few months now and one of every few builds that I push out through the new Test Flight in iTunes Connect can't be installed, and when I connect my device to my computer to look at the console, I see the error message
"Failed to verify code signature"
With the supplemental message:
Entitlements found that are not permitted by provisioning profile
I don't understand why this is an issue only sometimes. I seem to correct the issue by creating a new identical, aside from the build number, version and upload that.
What could I possibly be doing wrong? The only "entitlement" my app registers for is access to the keychain, but there is no toggle for that in the entitlements potion oft he application identifier on the developer portal.
I've downloaded the CloudKitAtlas sample code from Apple dated Sept 8. I did:
Setup the App ID
Enable the iCloud in Xcode capability
Setup the provisioning profile
Login to my iCloud Account in my Simulator (the different account from my developer account).
But the app crashes when I click the Discoverability in application. The error message is:
An error occured in requestDiscoverabilityPermission:: CKError
0x7fd7f162c1c0: "Not Authenticated" (9/1004); "Account couldn't get
container scoped user id, no underlying error received"; Retry after
3.0 seconds>
Do I miss anything setting up the iCloud? Thanks
I had the same problem on my app. Deleting the application from the simulator and restarting it fixed the problem. Take a clean build if necessary
Also, make sure that you are logged in to iCloud in Settings app.
Since upgrading to iOS 6 I have been unable to install the "TestFlight Access" profile, and my clients running 6.0 are experiencing the same issues. I have googled the issue but I am not finding any results.
The error message is just after you enter your device password and reads:
"Profile Installation Failed
A network error has occurred"
I have verified I have a good network connection, and the error is happening at multiple physical locations (different service providers and internet access)
Thanks in advance!
I just had the same problem with our build and one of our testers found this solution:
" advise people to go to settings > general > profiles and remove their profile and then clear cookies / cache, reboot the phone and it should work"
Make sure to remove the TestFlight WebClip profile as well.
Hope this helps!
Ryan