generated from grodin/kotlin-android-template
-
Notifications
You must be signed in to change notification settings - Fork 0
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
No charts loaded when user logs in #62
Labels
Comments
Possible solution: debug menu/drawer/settings screen with a simple option to add a load of data to the db |
On further investigation, this should have been at least showing an error message in the UI and surfaces a much more serious bug which is tracked in #70 |
grodin
pushed a commit
that referenced
this issue
Mar 23, 2022
grodin
pushed a commit
that referenced
this issue
Mar 23, 2022
Once integration testing #81 is set up it would be good to have a regression test to reproduce this |
grodin
pushed a commit
that referenced
this issue
Mar 10, 2023
grodin
pushed a commit
that referenced
this issue
Mar 10, 2023
I had implicitly assumed that a value class wrapping a String would simply return the wrapped String in a toString() call, but this is not the case. Fixes #62
grodin
pushed a commit
that referenced
this issue
Mar 14, 2023
grodin
pushed a commit
that referenced
this issue
Mar 14, 2023
I had implicitly assumed that a value class wrapping a String would simply return the wrapped String in a toString() call, but this is not the case. Fixes #62
grodin
pushed a commit
that referenced
this issue
Mar 14, 2023
grodin
pushed a commit
that referenced
this issue
Mar 14, 2023
I had implicitly assumed that a value class wrapping a String would simply return the wrapped String in a toString() call, but this is not the case. Fixes #62
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Caused by 97f570e which didn't change the deserialization code.This would have been caught by #39 Integration testing.This actually only comes up with data added to the emulator by an external script. There is a very minor bug in the representation of a
UserId
but there was no inconsistency; the same bug is used for both serialisation and deserialisation.This would not have been caught by testing, and arguably the bug is only in the db population script.
The underlying cause is that the script didn't use the same Firebase code that the app uses.
The solution then should be that if we need to pre-populate the db when using the emulator, that pre-population has to use the same code as the app.
The text was updated successfully, but these errors were encountered: