App Deployment and Testing
      Back to home
      1. Acrobits & Cloud Softphone FAQ
      2. Cloud Softphone (Business Solution) FAQ
      3. App Deployment and Testing

      How do I test/preview changes in the editable version of my Cloud Softphone app?

      Use the app’s editable version as a sandbox by provisioning with the asterisk. Sign in as username@CLOUDID* or pass * in the registration flow or QR/link to load editable settings.

      Note: The asterisk (*) tells the server to load the editable copy. Live remains unchanged.

      To easily preview changes; whether made by support or via ticket, before publishing, follow these steps:
      1. Log in using the editable account format

      Username: username@CLOUDID*

      • (Note: The asterisk (*) at the end is crucial — it signals the system to load the editable version.)
      • Password: Your usual SIP password

      Why this matters
       Without the *, your app will load the live production version, and changes won’t appear, even if they’ve been implemented.

      2.     Recommended workflow via the Web Portal
      • In the dashboard, click “Create Editable Copy” for your current version.
      • Use the editable login to test your modifications.
      • When ready, return to the portal and “Submit for Review”, then “Make LIVE” once approved. 
      Avoid these common mistakes: 
      • Don’t create a separate app just for testing. That risks duplicate billing and confusion.
      Don’t skip testing. Always confirm your changes appear as expected via editable login before launching in the app stores.
      Step-by-step workflow
      1. Open Cloud Softphone on your test device.
      2. Reset the app to force reprovisioning (then relaunch).
      3. Provision the editable version using one of the provisioning formats below.
        1. Classic initial screen (generic app): Enter your Cloud ID with an asterisk. Example: CLOUDID* plus your username and password.
        2. Registration Wizard (white label): Append * to the username/phone field. Example: +15551234567*. The app maps the * to the Cloud ID internally.
        3. QR code or link: Include the star in the code. Example: csc:username:password@CLOUDID*. If username/password are omitted, the app will prompt for them.
      4. Verify your changes in the app. If not visible, see Troubleshooting.
      5. When satisfied, promote changes from the portal using your normal release process.

      Troubleshooting

      • No changes visible: Recheck the star was used (*). Repeat provisioning and sign in again.
      • Signed into live by mistake: Reset, then provision with username@CLOUDID* (or add * in the wizard).
      • QR/link failed: Confirm the format is csc:username:password@CLOUDID* and retry.

      See also: How does External Provisioning work?