Unable to find content provider for username
Closed this issue · 4 comments
Everything seems to work fine except when we get to pilot. We are seeing this error.
[11:55:22]: [Transporter]: DBG-X: Apple's web service operation return value: [11:55:22]: [Transporter]: DBG-X: parameter ErrorMessage = Unable to find content provider for username [nate@some-email.com]. (1013) [11:55:22]: [Transporter]: DBG-X: parameter Errors = [Unable to find content provider for username [nate@some-email..com]. (1013)] [11:55:22]: [Transporter]: DBG-X: parameter ErrorCode = 1013 [11:55:22]: [Transporter]: DBG-X: parameter Success = false [11:55:22]: [Transporter Error Output]: Unable to find content provider for username [nate@some-email.com]. (1013) [11:55:22]: [Transporter]: DBG-X: The error code is: 1013 [11:55:22]: Transporter transfer failed.
Take a look at this SO thread for some tips on solving this issue: http://stackoverflow.com/questions/34157368/unable-to-find-content-provider-for-username-myusername-when-uploading-app-to
I appreciate the links - I had reviewed those solutions and working through them, I have still come up empty. It did give me some ideas that I will work through to make sure the certificates and provisions are correct on the machine in question. It is occurring with a colleague's computer , so I will post a follow up if we find a solution. Thank you.
This turned out to be an issue in how the script we were using was working. There were some hardcoded values that existed for the location of the provision (we have a multiple target/schema environment). This was causing issues with the content provider matching the correct username. Once I removed these values and let sign and cert to the downloading of the provisions, all was well.
This issue was migrated to fastlane/fastlane#3244. Please post all further comments there.
fastlane is now a mono repo, you can read more about the change in our blog post. All tools are now available in the fastlane main repo 🚀