I turned on Auto Update on my apps. I will be so glad that I can start
trusting that my users will use the newest versions of the app.
BUT, now I have the problem that now I am doing a lot of authoring of
adjustments to the forms and the app. And it's now time to do the TESTING
of those changes!
Now, normally I would "star" the newest testing release, update my 3
testing phones, and then quickly "unstar" the release.
But if I do that now, I am worried that some real mobile user on our
project (we have 110 users) might have his phone see the temporarily
"starred" release, and perform an update of the new (testing, likely not
correctly working) version!
-- What is the BEST way for me to conveniently download the new app version
to my testing phones, without the "star" risking real users get this "just
testing" version?
-- I really don't want to have to go to each of the phones, manage apps,
clear data, scan the NEW qr code for each phone, etc... that would drive me
crazy when there are 7 successive fixing versions...
-- I cannot use CloudCare for testing because my app uses case sharing
extensively and that is often what I am testing
... what's the best recommendation to handle this so I can test my changes
without going nuts?
I'll email you off-thread with some instructions that work well for this
use case. Also just wanted to note that you can use case sharing with
cloudcare (you just have to login with mobile workers instead of your
normal account). One easy way to do this is to keep a second window open in
incognito mode as a mobile worker.
Cory
···
On Mon, Sep 5, 2016 at 11:08 AM, Eric Stephan wrote:
Hi all --
I turned on Auto Update on my apps. I will be so glad that I can start
trusting that my users will use the newest versions of the app.
BUT, now I have the problem that now I am doing a lot of authoring of
adjustments to the forms and the app. And it's now time to do the TESTING
of those changes!
Now, normally I would "star" the newest testing release, update my 3
testing phones, and then quickly "unstar" the release.
But if I do that now, I am worried that some real mobile user on our
project (we have 110 users) might have his phone see the temporarily
"starred" release, and perform an update of the new (testing, likely not
correctly working) version!
-- What is the BEST way for me to conveniently download the new app
version to my testing phones, without the "star" risking real users get
this "just testing" version?
-- I really don't want to have to go to each of the phones, manage apps,
clear data, scan the NEW qr code for each phone, etc... that would drive me
crazy when there are 7 successive fixing versions...
-- I cannot use CloudCare for testing because my app uses case sharing
extensively and that is often what I am testing
... what's the best recommendation to handle this so I can test my changes
without going nuts?
I'd be interested in these notes too Cory, can you cc me in.
Thanks
Simon
···
On Monday, September 5, 2016 at 11:39:17 AM UTC+2, Cory Zue wrote:
>
> Hey Eric,
>
> I'll email you off-thread with some instructions that work well for this
> use case. Also just wanted to note that you can use case sharing with
> cloudcare (you just have to login with mobile workers instead of your
> normal account). One easy way to do this is to keep a second window open in
> incognito mode as a mobile worker.
>
> Cory
>
>
>
> On Mon, Sep 5, 2016 at 11:08 AM, Eric Stephan <estep...@gmail.com > wrote:
>
>>
>> Hi all --
>>
>> I turned on Auto Update on my apps. I will be so glad that I can start
>> trusting that my users will use the newest versions of the app.
>>
>> BUT, now I have the problem that now I am doing a lot of authoring of
>> adjustments to the forms and the app. And it's now time to do the TESTING
>> of those changes!
>>
>> Now, *normally* I would "star" the newest testing release, update my 3
>> testing phones, and then quickly "unstar" the release.
>>
>> But if I do that now, I am worried that some real mobile user on our
>> project (we have 110 users) might have his phone see the temporarily
>> "starred" release, and perform an update of the new (testing, likely not
>> correctly working) version!
>>
>> -- What is the BEST way for me to conveniently download the new app
>> version to my testing phones, without the "star" risking real users get
>> this "just testing" version?
>>
>> -- I really don't want to have to go to each of the phones, manage apps,
>> clear data, scan the NEW qr code for each phone, etc... that would drive me
>> crazy when there are 7 successive fixing versions...
>>
>> -- I cannot use CloudCare for testing because my app uses case sharing
>> extensively and that is often what I am testing
>>
>> ... what's the best recommendation to handle this so I can test my
>> changes without going nuts?
>>
>> THANKS!
>> Eric
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "commcare-users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to commcare-user...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
Looks like a number of people are interested in having this problem solved.
Hence we'll be releasing a small mobile feature that enables you to update
to a non-starred build in the upcoming CommCare 2.30 release, due out in a
few weeks from now.
In 2.30, you will be able to login, press 'Settings' under the '...' menu
button, and enable the newly added setting to update based off the latest
build on CommCareHQ, not the latest starred build.
···
On Tue, Sep 6, 2016 at 7:07 AM, Simon Berry wrote:
I'd be interested in these notes too Cory, can you cc me in.
Thanks
Simon
On Monday, September 5, 2016 at 11:39:17 AM UTC+2, Cory Zue wrote:
Hey Eric,
I'll email you off-thread with some instructions that work well for this
use case. Also just wanted to note that you can use case sharing with
cloudcare (you just have to login with mobile workers instead of your
normal account). One easy way to do this is to keep a second window open in
incognito mode as a mobile worker.
I turned on Auto Update on my apps. I will be so glad that I can start
trusting that my users will use the newest versions of the app.
BUT, now I have the problem that now I am doing a lot of authoring of
adjustments to the forms and the app. And it's now time to do the TESTING
of those changes!
Now, normally I would "star" the newest testing release, update my 3
testing phones, and then quickly "unstar" the release.
But if I do that now, I am worried that some real mobile user on our
project (we have 110 users) might have his phone see the temporarily
"starred" release, and perform an update of the new (testing, likely not
correctly working) version!
-- What is the BEST way for me to conveniently download the new app
version to my testing phones, without the "star" risking real users get
this "just testing" version?
-- I really don't want to have to go to each of the phones, manage apps,
clear data, scan the NEW qr code for each phone, etc... that would drive me
crazy when there are 7 successive fixing versions...
-- I cannot use CloudCare for testing because my app uses case sharing
extensively and that is often what I am testing
... what's the best recommendation to handle this so I can test my
changes without going nuts?
THANKS!
Eric
--
You received this message because you are subscribed to the Google
Groups "commcare-users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to commcare-user...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.