Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error in ODK Briefcase when pulling data in versions 11 to 13 #1519

Closed
bkimondiu opened this issue Dec 10, 2018 · 2 comments · Fixed by #1543
Closed

Error in ODK Briefcase when pulling data in versions 11 to 13 #1519

bkimondiu opened this issue Dec 10, 2018 · 2 comments · Fixed by #1543
Assignees
Labels

Comments

@bkimondiu
Copy link

bkimondiu commented Dec 10, 2018

The following error message is displayed in ODK Briefcase whenever versions 11 to 13 are used to pull data:

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://' ?

Aha! Link: https://ona.aha.io/features/PROD-287

@ukanga ukanga added this to the Week 01 - 02 (2019) milestone Jan 2, 2019
@lincmba lincmba self-assigned this Jan 8, 2019
@lincmba
Copy link
Contributor

lincmba commented Jan 9, 2019

After investigations, this is not an Onadata Issue but a Briefcase issue. The app fails without making a call to Onadata. It has been raised here https://github.com/opendatakit/briefcase/issues/695 .

@lincmba lincmba closed this as completed Jan 9, 2019
@ukanga
Copy link
Member

ukanga commented Jan 9, 2019

@lincmba Reopenning this one, see getodk/briefcase#695 (comment) for a way forward.

@ukanga ukanga reopened this Jan 9, 2019
lincmba added a commit that referenced this issue Jan 21, 2019
@lincmba lincmba added the Has-PR label Jan 21, 2019
lincmba added a commit that referenced this issue Jan 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants