Common Issues and Solutions When release Mobile Publishing

When creating a branded Now Mobile or Agent App in ServiceNow, you might encounter unexpected errors during the resigning and distribution process, especially for iOS builds. This article summarizes key issues I faced, and how to resolve them efficiently.

🛠️ Issue 1: Resigning Error – Code Object Not Signed

While following the KB article for iOS app resigning (KB0997467), I encountered this error in the Resigning Steps:

ServiceNow.xcarchive/Products/Applications/Requestor.app/Frameworks/AMBClient.framework: code object is not signed at all

✅ How to fix it:

Remove the existing certificate.
Re-add the certificate.
Rerun the Resigning Step.

This resolved the issue and allowed the resigning process to complete successfully.

🛠️ Issue 2: Xcode Error – Automatic Signing Cannot Update Bundle Identifier

When trying to validate or distribute the app in Xcode, I encountered this message:

Automatic signing cannot update bundle identifier Automatic signing cannot update your registered bundle identifier to enable Associated Domains, Siri, Data Protection, and Push Notifications. Update your bundle identifier on <https://developer.apple.com/account> and then try again

✅ How to fix it:

Go to Apple Developer Account - Bundle Identifiers.
Find your app’s Bundle ID.
Enable the following capabilities for your app:
- Associated Domains
- Siri
- Data Protection
- Push Notifications

After enabling these, Xcode was able to proceed with the validation and distribution process.

📝 Additional Resources

🎯 Summary

If you're working on a branded Now Mobile or Agent App, keep in mind these common pitfalls:

The Resigning Step may fail due to certificate issues—resetting the certificate usually fixes it.
Xcode may throw a bundle identifier error—update your app's capabilities in the Apple Developer portal to resolve it.

By applying these solutions, you can streamline the process and avoid unnecessary roadblocks.