Originally reported by: Yaw Anokwa (Bitbucket: yanokwa, GitHub: yanokwa)

<> says, "We should remove the branch in Core. Core repos should never contain branches. Also, it would appear that the documentation for getting started is not working as a result on this problem."

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/1

Originally reported by: Munaf Sheikh (Bitbucket: munafsheikh, GitHub: munafsheikh)

change name of javarosa-extras to javarosa-tools

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/8

Originally reported by: Yaw Anokwa (Bitbucket: yanokwa, GitHub: yanokwa)

it would be nice to support questions that can ask: "please rank the following options from 1 to n".

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/3

Originally reported by: Drew Roos (Bitbucket: mrgriscom, GitHub: mrgriscom)

javarosa should give warnings for any attributes it doesn't recognize inside javarosa/xforms tags.

right now it ignores them silently, so it makes it very hard to detect misspelled or unsupported attributes. for example:

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/39

Originally reported by: Yaw Anokwa (Bitbucket: yanokwa, GitHub: yanokwa)

When loading a form with arbitrary function calls, javarosa dies with an unhandled exception.
example where review() is the arbitrary function:

E/AndroidRuntime( 743): Uncaught handler: thread main exiting due to uncaught exception
E/AndroidRuntime( 743): org.javarosa.xpath.XPathUnhandledException: XPath evaluation: cannot handle function 'review'
E/AndroidRuntime( 743): at org.javarosa.xpath.expr.XPathFuncExpr.eval(XPathFuncExpr.java:155)
E/AndroidRuntime( 743): at org.javarosa.xpath.XPathConditional.evalRaw(XPathConditional.java:57)
E/AndroidRuntime( 743): at org.javarosa.xpath.XPathConditional.eval(XPathConditional.java:61)
E/AndroidRuntime( 743): at org.javarosa.core.model.FormDef.evaluateConstraint(FormDef.java:520)

This should be handled gracefully and either logged as a warning/error, or pushed through the UI to the user. Either way, the form should still work.

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/2

Originally reported by: Anonymous

After storing an unsent form that holds a input field of datatype 'long', i.e.

the form can't be opened again, neither can the 'saved forms' list, due to exception:

//unhandled exception in gui-cl => java.lang.RuntimeException[Error deserializing bytestream for type [fg]; No datatype registration to serialization code [c9 55 48 ff]]//

orignally posted at
https://groups.google.com/forum/#!topic/javarosa-developers/21iPw3gXmV8

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/47

Originally reported by: Munaf Sheikh (Bitbucket: munafsheikh, GitHub: munafsheikh)

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/17

Originally reported by: Yaw Anokwa (Bitbucket: yanokwa, GitHub: yanokwa)

for the trigger control it seems like jr j2meapp doesn't save anything in the instance.

that is, if i select "ok" after a trigger and i come back to that question, it doesn't remember that i clicked ok. might be good to have that data in the instance

also, if you mark a trigger as required, you can't go past it.

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/40

Originally reported by: Drew Roos (Bitbucket: mrgriscom, GitHub: mrgriscom)

i've discovered what i believe to be a bug in the propogation of chained conditions/relevancy. take the following form:

==========

#!xml

<h:html xmlns:h="http://www.w3.org/1999/xhtml"
        xmlns="http://www.w3.org/2002/xforms"
        xmlns:ev="http://www.w3.org/2001/xml-events"
        xmlns:xsd="http://www.w3.org/2001/XMLSchema"
        xmlns:jr="http://openrosa.org/javarosa">
<h:head>
  <h:title>group relevancy bug</h:title>
    <model>
      <instance>
        <form xmlns="">

<outer_trigger />
<inner_trigger />

<outer>
  <inner>
    <target_question />
  </inner>
  <inner_condition />
</outer>

<end />

        </form>
      </instance>
    
<bind nodeset="inner_trigger" type="int" />
<bind nodeset="outer/inner_condition" calculate="/form/inner_trigger &lt; 10" />
<bind nodeset="outer" relevant="../outer_trigger and ../outer_trigger != 'A'" />
<bind nodeset="outer/inner" relevant="../inner_condition" />
        
    </model>
</h:head>            
<h:body>

<input ref="inner_trigger"><label>inner trigger (enter 5)</label></input>
<input ref="outer_trigger"><label>outer trigger (enter 'D')</label></input>
<input ref="outer/inner/target_question"><label>target question: i am incorrectly skipped</label></input>
<input ref="end"><label>this is the end of the form</label></input>
   
</h:body>
</h:html>

==========

answer 5 for the first question, and 'D' for the second question. the 'target question' will be skipped, but i believe it should show up, since all the relevancy conditions for its containing groups ('inner' and 'outer') are satisfied.

the problem case above is pretty specific; namely, changing any of the following will cause target_question to show correctly:

• the relevancy of 'inner' must refer to a calculated node; putting the condition from inner_condition directly in the 'relevant' for 'inner' causes no bug
• the calculated node 'inner_condition' must be inside 'outer'. putting it at the top level does not trigger the bug
• inner_trigger must be asked before outer_trigger. switching the order causes no bug
• the relevancy of outer must start out false by default. changing the relevancy to just '../outer_trigger != 'A'' doesn't trigger the bug, as outer_trigger begins null, and null != 'A', thus making the 'outer' group relevant
• making inner_condition trivially dependent on outer_trigger doesn't cause the bug. i.e.,

i suspect that the problem comes from inner_condition initially being non-relevant by virtue of the containing group 'outer' being non-relevant. when 'outer' becomes relevant, the relevancy for its child nodes is not re-computed or was not pre-computed properly.

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/43

Originally reported by: Anonymous

Core code unable to get the appearance of group when there are no childs

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/46

Originally reported by: Brian DeRenzi (Bitbucket: bderenzi, GitHub: bderenzi)

change name of javarosa-extras to javarosa-tools

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/9

Originally reported by: Munaf Sheikh (Bitbucket: munafsheikh, GitHub: munafsheikh)

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/18

Originally reported by: Munaf Sheikh (Bitbucket: munafsheikh, GitHub: munafsheikh)

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/23

Originally reported by: Munaf Sheikh (Bitbucket: munafsheikh, GitHub: munafsheikh)

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/21

Originally reported by: routen (Bitbucket: routen, GitHub: routen)

j2meunit used by tests in the demo project, but not included with project, causes errors to appear in newbie environment (remove tests?)

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/32

Originally reported by: Munaf Sheikh (Bitbucket: munafsheikh, GitHub: munafsheikh)

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/27

Originally reported by: Munaf Sheikh (Bitbucket: munafsheikh, GitHub: munafsheikh)

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/12

Originally reported by: Munaf Sheikh (Bitbucket: munafsheikh, GitHub: munafsheikh)

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/25

Originally reported by: Yaw Anokwa (Bitbucket: yanokwa, GitHub: yanokwa)

if timestamps are not bound to dateTime, they will be likely default to null when restoring from saved data or anytime XFormAnswerDataParser:getAnswerData is called.

<bind nodeset="/d/ts" type="dateTime" jr:preload="timestamp" jr:preloadParams="now"/>

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/6

Originally reported by: Munaf Sheikh (Bitbucket: munafsheikh, GitHub: munafsheikh)

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/16

Originally reported by: Brian DeRenzi (Bitbucket: bderenzi, GitHub: bderenzi)

move validator and shellformtest to javarosa-validator repository

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/7

Originally reported by: routen (Bitbucket: routen, GitHub: routen)

j2merosa-libraries jar seems to need to be in the /lib folder rather than the /tools

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/33

Originally reported by: Munaf Sheikh (Bitbucket: munafsheikh, GitHub: munafsheikh)

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/22

Originally reported by: Natu Lauchande (Bitbucket: nlauchande, GitHub: nlauchande)

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/44

Originally reported by: Yaw Anokwa (Bitbucket: yanokwa, GitHub: yanokwa)

attached form crashes jr core with nullpointer exception at

java.lang.NullPointerException
       at org.javarosa.core.model.QuestionDef.localizeSelectMap(QuestionDef.java:259)
       at org.javarosa.xform.parse.XFormParser.parseControl(XFormParser.java:468)
       at org.javarosa.xform.parse.XFormParser$6.handle(XFormParser.java:120)
       at org.javarosa.xform.parse.XFormParser.parseElement(XFormParser.java:287)
       at org.javarosa.xform.parse.XFormParser.parseElement(XFormParser.java:296)
       at org.javarosa.xform.parse.XFormParser.parseElement(XFormParser.java:296)
       at org.javarosa.xform.parse.XFormParser.getFormDef(XFormParser.java:264)
       at org.javarosa.xform.parse.XFormParser.getFormDef(XFormParser.java:225)
       at org.javarosa.xform.util.XFormUtils.getFormFromInputStream(XFormUtils.java:50)

the problem is that one of the selects has a label but no items

<select1 ref="in14">
	<label ref="jr:itext('in14')"/>
</select1>

the core should throw a more useful error.

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/31

Originally reported by: Munaf Sheikh (Bitbucket: munafsheikh, GitHub: munafsheikh)

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/19

Originally reported by: Munaf Sheikh (Bitbucket: munafsheikh, GitHub: munafsheikh)

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/13

Originally reported by: Munaf Sheikh (Bitbucket: munafsheikh, GitHub: munafsheikh)

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/14

Originally reported by: Yaw Anokwa (Bitbucket: yanokwa, GitHub: yanokwa)

if you fill out a form with itext data for answers and restore it from xml, the answers displayed are "[itext:0]".

we discovered and fixed this in odk (see http://code.google.com/p/open-data-kit/issues/detail?id=45), but it should be fixed in the core.

<> suggests this fix in XFormAnswerDataParser.java:getSelection()

if (q != null) {
    if (q.getSelectItems() == null) {
        q.localizeSelectMap(null);
    }
    int index = q.getSelectedItemIndex(choice);
    s.attachQuestionDef(q);
    return (index != -1 ? s : null);
}
return true;

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/5

Originally reported by: Yaw Anokwa (Bitbucket: yanokwa, GitHub: yanokwa)

if you specify a jr:count and a jr:noaddremove="true()" on repeat x nested inside a repeat y, the repeat x will repeat forever.

removing jr:noaddremove has no effect on this bug.

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/4

Originally reported by: apoku (Bitbucket: apoku, GitHub: apoku)

Specifically when dynamically loading any number of forms, it is difficult to have the full JR experience on phones without GPRS service. As of now, once JR has been installed on the phone, the only dynamic option for loading new forms can occur by downloading forms over GPRS.

Proposal is for:

• A way one can load xforms into the application without
  pulling them down from a remote server.
• A way for Xforms to be transferred via USB
• Users should be able to load as many xform(s) as desired after JR has been installed (i.e. Xforms need not be bundled with local build).

See discussion on javaRosa-implementers google group:
http://groups.google.com/group/javarosa-implementers/browse_thread/thread/6d4883d226f645eb

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/49

Originally reported by: Munaf Sheikh (Bitbucket: munafsheikh, GitHub: munafsheikh)

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/11

Originally reported by: Yaw Anokwa (Bitbucket: yanokwa, GitHub: yanokwa)

according to the w3 spec, trailing white spaces needs to be removed.

<trailing_whitespace>
	trailing white space   
</trailing_whitespace>

should be the same as

<trailing_whitespace>trailing white space</trailing_whitespace>

currently, it is not.

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/50

Originally reported by: Munaf Sheikh (Bitbucket: munafsheikh, GitHub: munafsheikh)

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/26

Originally reported by: Munaf Sheikh (Bitbucket: munafsheikh, GitHub: munafsheikh)

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/24

Originally reported by: routen (Bitbucket: routen, GitHub: routen)

ZXing libs is currently assumed by the j2merosa-libraries jar, but needs to be obfuscated out?

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/35

Originally reported by: Acellam Guy (Bitbucket: mistaguy, GitHub: mistaguy)

The image widget does not activate the camera. am used a couple of Nokia phone of which N95 is among

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/45

Originally reported by: Yaw Anokwa (Bitbucket: yanokwa, GitHub: yanokwa)

currently, geopoint supports longitude, latitude, altitude and accuracy based on the length of the array. ideally, geo related attributes should be available independent of array length.

key value pairs seem like the best approach

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/37

Originally reported by: Munaf Sheikh (Bitbucket: munafsheikh, GitHub: munafsheikh)

for

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/30

Originally reported by: Yaw Anokwa (Bitbucket: yanokwa, GitHub: yanokwa)

on large forms with errors, it's difficult to track down where the error is without a line number.

http://groups.google.com/group/open-data-kit/browse_thread/thread/ae482f849b87580d is an example.

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/38

Originally reported by: Mathias Conradt (Bitbucket: mathiasconradt, GitHub: mathiasconradt)

When sending a form via SMS, the placeholder ${0} in message:

//sending.status.success = Successfully Submitted. Today we have received ${0} forms from you.
//

is not being replaced with the actual value.

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/48

Originally reported by: Anonymous

The new transport API should use the new storage API to leverage the advantages there. The transport API should nolonger store its own data but leave that to the new storage API

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/36

Originally reported by: Yaw Anokwa (Bitbucket: yanokwa, GitHub: yanokwa)

another issue. doesn't seem to work as a constraint. i understand i could use required=true(), but any reason why this doesn't work?

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/41

Originally reported by: Yaw Anokwa (Bitbucket: yanokwa, GitHub: yanokwa)

when parsing the media type, "image/*" is what the javarosa parser is looking for. it suggests that image/jpeg would work but it doesn't. maybe we can do an image/default and let the device decide what format it wants?

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/42

Originally reported by: Munaf Sheikh (Bitbucket: munafsheikh, GitHub: munafsheikh)

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/15

Originally reported by: Munaf Sheikh (Bitbucket: munafsheikh, GitHub: munafsheikh)

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/20

Originally reported by: Munaf Sheikh (Bitbucket: munafsheikh, GitHub: munafsheikh)

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/28

Originally reported by: Munaf Sheikh (Bitbucket: munafsheikh, GitHub: munafsheikh)

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/29

Originally reported by: routen (Bitbucket: routen, GitHub: routen)

it needs to be documented where to check/change paths to Polish and WTK

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/34

Originally reported by: Munaf Sheikh (Bitbucket: munafsheikh, GitHub: munafsheikh)

• Bitbucket: https://bitbucket.org/javarosa/javarosa/issue/10