-
Notifications
You must be signed in to change notification settings - Fork 17
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
Request gets 404 error #3
Comments
Please see instructions within this file https://github.com/ResearchStack/SampleApp/blob/0c19a34f5a0b4bcee4ea824a139ba5446b6f5b34/app/gradle.properties.sample |
I do have a gradle.properties file -- I put dummy strings in it |
I also tried: |
I have experienced the same issue. Thank you, |
The following values will not work.
You must change these to what is found within the Bridge Study Manager. These are used to tell the server that the data you are sending up belong to your study. The studyName can be found under Study > Settings > General > "Study name". The study identifier is also on the same page and is shown in the blurb on the right side of the page. A public bridge account does not exist for bridge communication at this time. However, providing the bridge schemas, or even a bridge setup doc, would be useful. @mikecarroll |
research.sagebridge.org requires that one log in. Same problem -- no password. Previous versions of the sample app did not have this problem. I assume that the bridge communication piece was just implemented. Can that implementation be removed, or can you tell us how to change the code ourselves? I have looked into this, and it is not obvious. |
Correct, we were using the credentials for mole mapper while SampleApp was in development. This needed to be removed for when we open sourced the code. Sage Bridge is the backend servcie that can be used for sign-in, sign-up, consent, and data upload. It only exists within the App and you are free to implement your own code for data upload. While it can be removed, it will be quite a bit of work. You will need to implement DataProvider and return that within the ResearchStack instance. |
Thank you. It seems to me that SampleApp now has substantially reduced utility for new app developers. |
Yes, this is a limitation with the SampleApp, as it stands. We built our tests apps against Sage Bridge (which MoleMapper uses) but haven't had the cycles to build a version that doesn't require a Sage account or backend for the signup process yet. Two thoughts: (1) ResearchStack is backend agnostic so have a mock DataProvider for the SampleApp and basic dev would be an amazing conribution, if somebody wants to build it. @dariosalviwork originally proposed the idea here, and we would be excited to accept a PR to the SampleApp for it. (2) Since @crayne raised this issue, I've been talking with Sage about making the initial dev process against Bridge easier and they have some potential solutions in the works that I hope we can implement here soon. |
can anyone repeat the solution for this problem?? I am not being able to solve this problem. |
I have created a file named gradle.properties and have included the following values: studyId="bridge_study_id" but this doesn't seem to solve the problem. Can you please give me any suggestion to solve the problem? @wdziemia |
@DP0326 I'd be happy to help but won't have time until late next week at the earliest. For now, I'd suggest looking at the pull requests for this repo. This should address most of the issues. |
Hi,
Thank you for your prompt reply. But I need to solve this problem by this
Friday. Anykind of help will be appreciated.
…On 17 Jul 2019 17:57, "Joshua Liu" ***@***.***> wrote:
@DP0326 <https://github.com/DP0326> I'd be happy to help but won't have
time until late next week at the earliest.
For now, I'd suggest looking at the pull requests for this repo
<https://github.com/ResearchStack/MoleMapperAndroid/pulls>. This should
address most of the issues.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3?email_source=notifications&email_token=AMUGR4QUVXGRJV7NHOCZODLP76PULA5CNFSM4CBXYRE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2G2EQI#issuecomment-512598593>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AMUGR4RRVKW7KKFAFECIBDTP76PULANCNFSM4CBXYREQ>
.
|
POST:
The text was updated successfully, but these errors were encountered: