Editing and testing APPS

Avatar
Matt Good

Whenever I edit an app and save my changes, the app version increments even if I haven't published it. If I make several changes today, then go in tomorrow to continue editing, then publish to testing, then make corrections, etc, my version numbers jump up in ridiculous blocks. Saving changes and publishing to testing should only change the version number once until that version has been published to ALL users, not just testing. And how am I supposed to test my new apps BEFORE publishing them if I cannot publish a new app to testing before publishing it to all users?

2

Comments

3 comments

Sort by Date Votes
  • Avatar
    Lauren Sunday

    Hey Matt,

    Increasing your editing version is not necessarily a bad thing! If you are not publishing between every change, if the app is not in active use, then you only need to save it to keep progress and pick it up the next day. As for testing, there is a Testing Mode you can activate from your account settings that allows you to test out changes before publishing. This allows you to make sure changes you made work before publishing to everyone. 

    We are definitely aware of this and the frustrations it raises to have to publish or publish for testing every time you want to make sure an edit works. We are working on correcting this long-term from within the App Builder. Please keep an eye out for updates regarding these improvements!

    0
    Comment actions Permalink
  • Avatar
    BRET GRAHAM

    To Matt's point, the times that you "Publish to Testing" and then return to edit and "Publish to Testing" does increase the version. It should not increase by a full number until published, e.g. Version 1, edit, "Publish to Testing", should now show as Version 1.1, or 1a, and should not increment to Version 2 until publish to all users. I have upvoted Matt's request. 

    1
    Comment actions Permalink
  • Avatar
    Lauren Sunday

    Hi Bret,

    While I do agree that it is frustrating that it increases the version, I'm not sure if creating sub-versions like 1.1 or 1a would solve any of the issues that may be created by increasing the version. That would still technically be a new version on the backend. But I can raise this request with the product team and see if this is something that is technically possible or not. 

    0
    Comment actions Permalink

Please sign in to leave a comment.