-
Notifications
You must be signed in to change notification settings - Fork 154
Invalid url error when pulling data from server #695
Comments
Thanks for reporting this issue, @lincmba! Could you add the URL are you trying to use? Also, could you attach the |
@ggalmazor , thanks for the quick response. The url is For <v1.10 For later versions |
@lincmba I see this seems only to happen when the form in <xform>
<formID>south</formID>
<name>south</name>
<version>201709072011</version>
<hash>md5:cbddab1c170b3406ee4bbfac3b89cb4a</hash>
<descriptionText />
<downloadUrl>https://odk.ona.io/..../form.xml</downloadUrl>
<manifestUrl />
</xform> Propably the approach we should take on the onadata side is not include the <xform>
<formID>south</formID>
<name>south</name>
<version>201709072011</version>
<hash>md5:cbddab1c170b3406ee4bbfac3b89cb4a</hash>
<downloadUrl>https://odk.ona.io/..../form.xml</downloadUrl>
</xform> @ggalmazor What I am wondering, should ODK Briefcase bulk at empty XML tags e.g |
Here's the |
@ggalmazor Here are detailed steps to reproduce this: On Onadata
On Briefcase
|
I've sent #704 to make Briefcase ignore empty manifest tags in the form's XML, but I can't really reproduce the error you're reporting following your steps list. Could you verify that this is still happening? Maybe Ona has changed something and now there's no manifest url tag in the response. Can you confirm this, @ukanga? |
Software versions
from Briefcase v1.11.0 to v1.13.1
Problem description
Pulling data from the server fails. Here's the detailed status
Fetching form definition resolving against briefcase form definitions Fetching form manifest Error fetching form definition: Fetch of manifest failed. Detailed reason: Invalid url. Failed with error: no protocol: . Did you forget to prefix the address with 'http://' or 'https://' ?
Only one of the two api calls are made to the server.
Steps to reproduce the problem
Configure briefcase with Aggregate Server
Provide right credentials to an account with forms
Pull form
Expected behavior
Should pull forms with the final status 'SUCCESS'
The text was updated successfully, but these errors were encountered: