Bunch of fixes from the NREL branch #737
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Launch a survey - Autogenerate a random token - Change the text on the login page - Display the random token for the user to enter - Once we have the newer version of emTripLog, we can set this automatically
Finally we get to use the new `setPromptedAuthToken` method. This raises a bunch of new questions: - if the user switches phones or uninstalls + reinstalls, how do they enter their old token? - how do they write their old token down - should we give them a choice between autogenerated and human generated Fortunately, since this is going to collect data for 2-3 days, none of these need to be answered right now.
This allow users to answer the survey in-app even if they are not able to respond to the push notification in real time Testing done: - Launched the app - Clicked on the button - Confirmed that the weekly survey was launched
+ add a button to launch the survey from the profile so current users can fill it in Testing done: - launched survey during onboarding + from the profile screen - confirmed with Bingrong that the UUID was filled in This partially fixes e-mission/e-mission-docs#587 Full fix will involve updating the documentation
Avoids race conditions and confusion; highlights the diary We may want to merge this to master based on feedback from the CEO project
Can change this based on feedback from initial testers
While matching user inputs on the server, found that user input matching was broken for some cleaned trips on the phone. e-mission/e-mission-docs#476 (comment) Expanded the user input end check to fix. e-mission/e-mission-docs#476 (comment) Will merge into master after additional testing on the branch. + bump up the allowed delta to 15 minutes since the time threshold default for the distance filter is 10 minutes.
The enhanced trip matching (75129db) caused a regression in which a spurious trip (not a trip) that occurred after the real trip fit the criteria for a match. And since it was confirmed after the real trip, as you would expect while going down the trip list, it was matched preferentially. e-mission/e-mission-docs#476 (comment) Fixed by checking the degree over overlap and rejecting too short matches
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Including: