Wanted to report a bug and workaround for a case's detail/list view that
caused force crash while opening forms that require a case.
error message:
"The application Commcare ODK (process.org.commcare.dalvlk) has stopped
unexpectedly. Please try again."
I have a few forms within a module, one that opens the case and 2 others
that require a case. Every form updates info to the cases.
After changing a bunch of variables in the first form that "opens a case"
and "updates the case," I was unable to open the subsequent forms that
required the case. Crashed just after clicking the form and before
entering the list view.
I thought it was strange that i could open the first form, but not the
other two... and figured it must be something with the case list/detail
view defined at the bottom of the module. After deleting all the case
properties and re-adding them, it no longer crashed.
If there is a way to check for this in the compiler, I think it would help
a lot of people. I've had this bug for a while and was reverting back to
working versions before. Finally figured it out.. at least a simpler fix.
Sorry about the problems here, it sounds like you triggered a bug in the
app builder that let you build an app that wasn't valid! Can you let us
know what your domain/project are and the number of one of the broken
builds so we can take a look at how it was invalid? We'll fix the app
builder so this problem won't occur int he future.
Thanks!
-Clayton
···
On Thu, Apr 11, 2013 at 7:34 AM, Greg Tao wrote:
Wanted to report a bug and workaround for a case's detail/list view that
caused force crash while opening forms that require a case.
error message:
"The application Commcare ODK (process.org.commcare.dalvlk) has stopped
unexpectedly. Please try again."
I have a few forms within a module, one that opens the case and 2 others
that require a case. Every form updates info to the cases.
After changing a bunch of variables in the first form that "opens a case"
and "updates the case," I was unable to open the subsequent forms that
required the case. Crashed just after clicking the form and before
entering the list view.
I thought it was strange that i could open the first form, but not the
other two... and figured it must be something with the case list/detail
view defined at the bottom of the module. After deleting all the case
properties and re-adding them, it no longer crashed.
If there is a way to check for this in the compiler, I think it would help
a lot of people. I've had this bug for a while and was reverting back to
working versions before. Finally figured it out.. at least a simpler fix.
You can use the "Report an Issue" button in the lower right to make sure we
can track the issue.
thanks,
Jonathan
Jonathan L. Jackson
Chief Executive Officer
Dimagi, Inc | 585 Massachusetts Ave | Suite 3 | Cambridge, MA 02139
t: (617) 492 2214 | m: (617) 596 6243
web: http://www.dimagi.com/
···
On Thu, Apr 11, 2013 at 10:55 AM, Clayton Sims wrote:
Greg,
Sorry about the problems here, it sounds like you triggered a bug in the
app builder that let you build an app that wasn't valid! Can you let us
know what your domain/project are and the number of one of the broken
builds so we can take a look at how it was invalid? We'll fix the app
builder so this problem won't occur int he future.
Wanted to report a bug and workaround for a case's detail/list view that
caused force crash while opening forms that require a case.
error message:
"The application Commcare ODK (process.org.commcare.dalvlk) has stopped
unexpectedly. Please try again."
I have a few forms within a module, one that opens the case and 2 others
that require a case. Every form updates info to the cases.
After changing a bunch of variables in the first form that "opens a case"
and "updates the case," I was unable to open the subsequent forms that
required the case. Crashed just after clicking the form and before
entering the list view.
I thought it was strange that i could open the first form, but not the
other two... and figured it must be something with the case list/detail
view defined at the bottom of the module. After deleting all the case
properties and re-adding them, it no longer crashed.
If there is a way to check for this in the compiler, I think it would
help a lot of people. I've had this bug for a while and was reverting back
to working versions before. Finally figured it out.. at least a simpler
fix.
Sure, will do. My project is called "test-space" - OttoClave App. I
think it's builds 372, 373, 378, 391, 394. I finally fixed it in 396 by
deleting everything in the list/detail view and adding just one field.
-Greg
···
On Thursday, April 11, 2013 10:57:35 PM UTC+8, Jonathan Jackson wrote:
>
> Hi Greg -
>
> You can use the "Report an Issue" button in the lower right to make sure
> we can track the issue.
>
> thanks,
> Jonathan
>
>
> Jonathan L. Jackson
> Chief Executive Officer
> Dimagi, Inc | 585 Massachusetts Ave | Suite 3 | Cambridge, MA 02139
> t: (617) 492 2214 | m: (617) 596 6243
> web: http://www.dimagi.com/
>
>
> On Thu, Apr 11, 2013 at 10:55 AM, Clayton Sims <cs...@dimagi.com wrote:
>
>> Greg,
>>
>> Sorry about the problems here, it sounds like you triggered a bug in the
>> app builder that let you build an app that wasn't valid! Can you let us
>> know what your domain/project are and the number of one of the broken
>> builds so we can take a look at how it was invalid? We'll fix the app
>> builder so this problem won't occur int he future.
>>
>> Thanks!
>> -Clayton
>>
>>
>> On Thu, Apr 11, 2013 at 7:34 AM, Greg Tao <greg...@gmail.com wrote:
>>
>>> Wanted to report a bug and workaround for a case's detail/list view that
>>> caused force crash while opening forms that require a case.
>>>
>>> error message:
>>> "The application Commcare ODK (process.org.commcare.dalvlk) has stopped
>>> unexpectedly. Please try again."
>>>
>>> I have a few forms within a module, one that opens the case and 2 others
>>> that require a case. Every form updates info to the cases.
>>>
>>> After changing a bunch of variables in the first form that "opens a
>>> case" and "updates the case," I was unable to open the subsequent forms
>>> that required the case. Crashed just after clicking the form and before
>>> entering the list view.
>>>
>>> I thought it was strange that i could open the first form, but not the
>>> other two... and figured it must be something with the case list/detail
>>> view defined at the bottom of the module. After deleting all the case
>>> properties and re-adding them, it no longer crashed.
>>>
>>> If there is a way to check for this in the compiler, I think it would
>>> help a lot of people. I've had this bug for a while and was reverting back
>>> to working versions before. Finally figured it out.. at least a simpler
>>> fix.
>>>
>>> -Greg
>>>
>>>
>>> --
>>> 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/groups/opt_out.
>>>
>>>
>>>
>>
>> --
>> 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/groups/opt_out.
>>
>>
>>
>
>
I've confirmed that the app was building incorrectly in those versions and
forwarded that information along to our server team. They'll get the issue
resolved ASAP so it won't occur again in the future.
Thanks!
-Clayton
···
On Thu, Apr 11, 2013 at 11:23 AM, Greg Tao wrote:
Sure, will do. My project is called "test-space" - OttoClave App. I
think it's builds 372, 373, 378, 391, 394. I finally fixed it in 396 by
deleting everything in the list/detail view and adding just one field.
-Greg
On Thursday, April 11, 2013 10:57:35 PM UTC+8, Jonathan Jackson wrote:
Hi Greg -
You can use the "Report an Issue" button in the lower right to make sure
we can track the issue.
thanks,
Jonathan
Jonathan L. Jackson
Chief Executive Officer
Dimagi, Inc | 585 Massachusetts Ave | Suite 3 | Cambridge, MA 02139
t: (617) 492 2214 | m: (617) 596 6243
web: http://www.dimagi.com/
On Thu, Apr 11, 2013 at 10:55 AM, Clayton Sims cs...@dimagi.com wrote:
Greg,
Sorry about the problems here, it sounds like you triggered a bug in the
app builder that let you build an app that wasn't valid! Can you let us
know what your domain/project are and the number of one of the broken
builds so we can take a look at how it was invalid? We'll fix the app
builder so this problem won't occur int he future.
Wanted to report a bug and workaround for a case's detail/list view
that caused force crash while opening forms that require a case.
error message:
"The application Commcare ODK (process.org.commcare.**dalvlk) has
stopped unexpectedly. Please try again."
I have a few forms within a module, one that opens the case and 2
others that require a case. Every form updates info to the cases.
After changing a bunch of variables in the first form that "opens a
case" and "updates the case," I was unable to open the subsequent forms
that required the case. Crashed just after clicking the form and before
entering the list view.
I thought it was strange that i could open the first form, but not the
other two... and figured it must be something with the case list/detail
view defined at the bottom of the module. After deleting all the case
properties and re-adding them, it no longer crashed.
If there is a way to check for this in the compiler, I think it would
help a lot of people. I've had this bug for a while and was reverting back
to working versions before. Finally figured it out.. at least a simpler
fix.
-Greg
--
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.
--
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.
Thanks for your support. Really appreciate it. I figured out the
workaround for now. Just trying to post to help others.
Best,
Greg
···
On Saturday, April 13, 2013 1:28:25 AM UTC+8, Clayton Sims wrote:
>
> Greg,
>
> I've confirmed that the app was building incorrectly in those versions and
> forwarded that information along to our server team. They'll get the issue
> resolved ASAP so it won't occur again in the future.
>
> Thanks!
> -Clayton
>
>
> On Thu, Apr 11, 2013 at 11:23 AM, Greg Tao <greg...@gmail.com wrote:
>
>> Sure, will do. My project is called "test-space" - OttoClave App. I
>> think it's builds 372, 373, 378, 391, 394. I finally fixed it in 396 by
>> deleting everything in the list/detail view and adding just one field.
>>
>> -Greg
>>
>>
>> On Thursday, April 11, 2013 10:57:35 PM UTC+8, Jonathan Jackson wrote:
>>
>>> Hi Greg -
>>>
>>> You can use the "Report an Issue" button in the lower right to make sure
>>> we can track the issue.
>>>
>>> thanks,
>>> Jonathan
>>>
>>>
>>> Jonathan L. Jackson
>>> Chief Executive Officer
>>> Dimagi, Inc | 585 Massachusetts Ave | Suite 3 | Cambridge, MA 02139
>>> t: (617) 492 2214 | m: (617) 596 6243
>>> web: http://www.dimagi.com/
>>>
>>>
>>> On Thu, Apr 11, 2013 at 10:55 AM, Clayton Sims wrote:
>>>
>>>> Greg,
>>>>
>>>> Sorry about the problems here, it sounds like you triggered a bug in
>>>> the app builder that let you build an app that wasn't valid! Can you let us
>>>> know what your domain/project are and the number of one of the broken
>>>> builds so we can take a look at how it was invalid? We'll fix the app
>>>> builder so this problem won't occur int he future.
>>>>
>>>> Thanks!
>>>> -Clayton
>>>>
>>>>
>>>> On Thu, Apr 11, 2013 at 7:34 AM, Greg Tao wrote:
>>>>
>>>>> Wanted to report a bug and workaround for a case's detail/list view
>>>>> that caused force crash while opening forms that require a case.
>>>>>
>>>>> error message:
>>>>> "The application Commcare ODK (process.org.commcare.**dalvlk) has
>>>>> stopped unexpectedly. Please try again."
>>>>>
>>>>> I have a few forms within a module, one that opens the case and 2
>>>>> others that require a case. Every form updates info to the cases.
>>>>>
>>>>> After changing a bunch of variables in the first form that "opens a
>>>>> case" and "updates the case," I was unable to open the subsequent forms
>>>>> that required the case. Crashed just after clicking the form and before
>>>>> entering the list view.
>>>>>
>>>>> I thought it was strange that i could open the first form, but not the
>>>>> other two... and figured it must be something with the case list/detail
>>>>> view defined at the bottom of the module. After deleting all the case
>>>>> properties and re-adding them, it no longer crashed.
>>>>>
>>>>> If there is a way to check for this in the compiler, I think it would
>>>>> help a lot of people. I've had this bug for a while and was reverting back
>>>>> to working versions before. Finally figured it out.. at least a simpler
>>>>> fix.
>>>>>
>>>>> -Greg
>>>>>
>>>>>
>>>>> --
>>>>> 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/**groups/opt_out
>>>>> .
>>>>>
>>>>>
>>>>>
>>>>
>>>> --
>>>> 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/**groups/opt_out
>>>> .
>>>>
>>>>
>>>>
>>>
>>> --
>> 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/groups/opt_out.
>>
>>
>>
>
>