Skip to main content

Overview

Once you’ve registered mobile apps in Bit2Connect, you can reuse them across multiple dynamic links by referencing their IDs. This approach simplifies link creation and ensures consistency.

Benefits of Using Saved Apps

Simplified API Calls

Reference apps by ID instead of providing full configuration every time.

Consistency

All links use the same app configuration, ensuring consistent behavior.

Easy Updates

Update app configuration once to affect all associated links.

Reduced Errors

No risk of typos in bundle IDs or package names when reusing saved apps.

Basic Usage

Step 1: List Available Apps

First, retrieve your saved mobile apps to get their IDs:
cURL
Response
Use the app IDs when creating dynamic links:
cURL
Automatic Configuration: When you provide iosAppId or androidAppId, the platform automatically loads and applies the saved app configuration.

Advanced Patterns

Pattern 1: iOS Only

Create a link that only supports iOS deep linking:

Pattern 2: Android Only

Create a link that only supports Android deep linking:

Pattern 3: Both Platforms

Support both iOS and Android with a single link:

Pattern 4: Mixed Configuration

Combine saved apps with additional link-specific settings:

Implementation Examples

JavaScript/Node.js

Python

PHP

Best Practices

Environment Variables: Store app IDs in environment variables or configuration files, not hardcoded in your application.
Caching: Cache the list of mobile apps locally to avoid repeated API calls when creating multiple links.
Validation: Always validate that your saved app IDs exist before creating links in production.
Fallback Strategy: Consider implementing a fallback to manual configuration if saved app lookup fails.

Migration from Manual to Saved Apps

If you’re currently using manual configuration, here’s how to migrate:

Step 1: Audit Current Configuration

Review your current link creation code to identify common mobile app configurations.

Step 2: Create Mobile Apps

Register your mobile apps once:

Step 3: Update Your Code

Replace manual configuration with app IDs:

Troubleshooting

App Not Found Error

If you receive an “App not found” error:
  1. Verify the app ID is correct
  2. Ensure the app belongs to your project
  3. Check that the app hasn’t been deleted

Configuration Not Applied

If mobile app configuration isn’t being applied:
  1. Verify you’re using iosAppId/androidAppId (not ios/android objects)
  2. Check that the saved app has valid configuration
  3. Review the link response to confirm app association

Mixed Configuration Conflicts

When using both iosAppId and manual ios configuration:
  • Saved App Takes Priority: The iosAppId configuration will override manual settings
  • Best Practice: Use either saved apps OR manual configuration, not both

Next Steps