iOS error signing requires a development team

[rpuls]

Finally got a bit further! Conclusion is that the react-native cli doesn’t generate a sufficient project.pbxproj file, which means that one must load the project in latest version of Xcode installed on a mac. Xcode will then resolve the project.pbxproj file and save it in a working condition. This could perhaps some how be handled in a bitrise workflow module? Completely eliminating the need to own a physical mac I installed Mojave on virtualBox on my windows, and did the fix there…

I also did a side by side comparison of the old and the new configuration file, there is too much going on for me to understand it, and for that reason i don’t think it can be configured manually (at least not by most people)…

Anyway… My Xcode archive step is still not succeeding

error: No profiles for ‘com.dashboardwrapper’ were found: Xcode couldn’t find any iOS App Development provisioning profiles matching ‘com.dashboardwrapper’. Automatic signing is disabled and unable to generate a profile. To enable automatic signing, pass -allowProvisioningUpdates to xcodebuild. (in target ‘dashboardwrapper’)

I am not sure why it can’t find the matching provisioning profile. com.dashboardwrapper is my app id and inside my provisioning profile this app id is the same, except that the team id is dot concatenated in the start of the app id.

<key>Entitlements</key>
<dict>
					<key>application-identifier</key>
	<string>D97F7P64UX.com.dashboardwrapper</string>
					<key>keychain-access-groups</key>
	<array>
			<string>D97F7P64UX.*</string>
	</array>
					<key>get-task-allow</key>
	<true/>
					<key>com.apple.developer.team-identifier</key>
	<string>D97F7P64UX</string>

So my quetsion is maybe, why is the xcode archive step looking for a proffile matching com.dashboardwrapper and not D97F7P64UX.com.dashboardwrapper - or is that actually expected behavior?

Build log: Bitrise - Mobile Continuous Integration and Delivery - iOS & Android Build Automation

Cheers!

[fehersanyi-bitrise]

Hy, yes, the bundle id is usually named in this manner, and it (as far as I know) never holds the team id
aslo your bundle id in the installed profile is com.dashboardwrapper as well.
could you just remove D97F7P64UX. from the plist file?

[rpuls]

The text from above is from within the provisioning file “engieneering.mobileprovision” the one download from the apple developer console. My info.plist doesn’t contain any ids it seems

this is the entire file:
<?xml version=“1.0” encoding=“UTF-8”?>
<!DOCTYPE plist PUBLIC “-//Apple//DTD PLIST 1.0//EN” “http://www.apple.com/DTDs/PropertyList-1.0.dtd”>
<plist version=“1.0”>
<dict>
<key>CFBundleDevelopmentRegion</key>
<string>en</string>
<key>CFBundleDisplayName</key>
<string>dashboardwrapper</string>
<key>CFBundleExecutable</key>
<string>$(EXECUTABLE_NAME)</string>
<key>CFBundleIdentifier</key>
<string>$(PRODUCT_BUNDLE_IDENTIFIER)</string>
<key>CFBundleInfoDictionaryVersion</key>
<string>6.0</string>
<key>CFBundleName</key>
<string>$(PRODUCT_NAME)</string>
<key>CFBundlePackageType</key>
<string>APPL</string>
<key>CFBundleShortVersionString</key>
<string>1.0</string>
<key>CFBundleSignature</key>
<string>???</string>
<key>CFBundleVersion</key>
<string>1</string>
<key>LSRequiresIPhoneOS</key>
<true/>
<key>NSLocationWhenInUseUsageDescription</key>
<string/>
<key>UILaunchStoryboardName</key>
<string>LaunchScreen</string>
<key>UIRequiredDeviceCapabilities</key>
<array>
<string>armv7</string>
</array>
<key>UISupportedInterfaceOrientations</key>
<array>
<string>UIInterfaceOrientationPortrait</string>
<string>UIInterfaceOrientationLandscapeLeft</string>
<string>UIInterfaceOrientationLandscapeRight</string>
</array>
<key>UIViewControllerBasedStatusBarAppearance</key>
<false/>
<key>NSAppTransportSecurity</key>
<dict>
<key>NSAllowsArbitraryLoads</key>
<true/>
<key>NSExceptionDomains</key>
<dict>
<key>localhost</key>
<dict>
<key>NSExceptionAllowsInsecureHTTPLoads</key>
<true/>
</dict>
</dict>
</dict>
<key>UIAppFonts</key>
<array>
…
</array>
</dict>
</plist>

[fehersanyi-bitrise]

Could you please enable support user on the app? I would like to check out your setup and run a few test builds if it’s ok with you

[rpuls]

Support user enabled.

[fehersanyi-bitrise]

are you sure? I can’t reach your app

[rpuls]

Oh, you are right sorry, think something went wrong:

Sorry, we are not sure if enabling the support user was successful (it might take some time.) Please refresh the page and check the state of the toggle.

[rpuls]

It looks to be enabled now!

[fehersanyi-bitrise]

Could you please connect your apple developer account to bitrise?

[rpuls]

Done, that certainly looks different in the build process, it did find the profile, but now the setting are conflicting because there is both auto turned on and a specified provisioning profile. What should i remove from the workflow now ?

[fehersanyi-bitrise]

what I think, is that you are using xcode managed signing locally, and I would try to build with the ios auto provisioning step, but that needs the apple account connected

ps I have a good feeling now, it did not crash at the same stage now

[rpuls]

great! so just to be sure… I have to replace both Certificate and profile installer and Xcode Archive & Export for iOS with just iOS Auto Provision ?

[fehersanyi-bitrise]

no no, just the certificate and profile installer, that will get the profile/generate an appropriate one for the project, from the developer portal so it is sure to be good. also you will need to upload a deployment certificate to the code signing tab to be able to generate an app-store ipa in the future!

ps: I see you are on a free plan and the ten minutes will not be enough to build
I recommend doing a few referrals so you get some extra build time

[rpuls]

No worries have gotten approval for upgrading to paid plan.

[fehersanyi-bitrise]

Sounds good, if you do that, I am sure you will be able to build successfully now, get back to me please when you upgraded the plan and we can check it out to be sure

[rpuls]

Thanks for your great support! Worked like a charm. Auto provision is waaaaay less complicated than the manual procedure. Should have known this earlier

[fehersanyi-bitrise]

I’m really glad we could solve this issue!