Modifying Apps with Frameworks that Don't Allow Bundle ID Changes
Modifying apps that have frameworks that don’t allow bundle ID changes can potentially lead to application errors if these modifications are not done properly.
This Knowledge Base article summarizes how Appdome automatically detects when certain frameworks do not allow bundle ID changes in advance, thereby avoiding potential error conditions which may otherwise have occurred.
We hope you find it useful and enjoy using Appdome!
Working with Apps that Don’t Allow Bundle ID Changes
Using a simple ‘click to add’ user interface, Appdome allows anyone to easily enhance an app with frameworks that don’t allow bundle ID changes – instantly, no code or coding required.
Using Appdome, there are no development or coding prerequisites. For example, there is no Appdome SDK, libraries, or plug-ins to implement. There are no additional development requirements to Fuse a mobile app that will not accept bundle ID changes with additional features and integrations. The Appdome technology adds relevant standards, frameworks and more to the app automatically, with no manual development work at all.
Building Mobile Apps that Don’t Accept Bundle ID Changes with Additional Features Fast
Information on Mobile Apps’ Frameworks and How They Can Use Bundle IDs
- Some app frameworks enforce app licensing by specific app bundle IDs.
- A bundle ID is a unique identifier for an app usually written in reverse DNS notation like com.appdome.example
- Appdome provides the capability to modify an app bundle ID.
- However, some apps utilize frameworks that do not permit their bundle ID to be changed.
- Appdome will detect these frameworks and prevent the bundle ID from being changed.
- One of these frameworks is PSPDFKit.
- For more information on this framework, you can visit this resource. We will continue adding more frameworks to Appdome.
Prerequisites for using Appdome for Bundle ID Changes
In order to use Appdome’s no code implementation to modify apps that don’t allow bundle ID changes, you’ll need:
How to Build Apps with Frameworks Not Allowing Bundle ID Changes Without Errors
- Upload a Mobile App to Your Account
- From the “Build” tab, add Features and Services to your App
Select the Build Tab. Beneath it, you will find several service options. Select the ones you’d like applied to your app then Build My App!
Congratulations! You now have a mobile app fully integrated with the features you selected even when it didn’t accept bundle ID changes.
The technology behind Build My App has two major elements – (1) a microservice architecture filled with 1000s of code sets needed for mobile integrations, and (2) an adaptive code generation engine that can recognize the development environment.
Add Context™ to the Appdome-Built App
Appdome is a full-featured mobile integration platform. Within Context™, Appdome users can brand the app, including adding a favicon to denote the new service added to the app.
For more information on the range of options available in Context™, please read this knowledge base article.
Sign the Appdome Built App (Required)
In order to deploy an Appdome Built app, it must be signed. Signing iOS apps and Signing Android apps are easy using Appdome. Alternatively, you can use Private Signing, download your unsigned app and sign locally using your own signing methods.
Deploy the Appdome-Built App to a Mobile Device
Once you have signed your Appdome-Built app, you can download to deploy it using your distribution method of choice. For more information on deploying your Appdome-Built apps, please read this knowledge base.
How Do I Learn More?
For more information on this topic, visit Appdome for Enterprise Mobility on our website.
If you have any questions, please send them our way at firstname.lastname@example.org or via the chat window on the Appdome platform.