Closed AnnieMungai closed 3 years ago
@ellykits cc @tychus6 I checked out these users on the OpenSRP web and this is what I found: Zacharia is assigned in both teams. Elina - only on Linda clinic (I am not sure how to check whether they are assigned to another team) Theresa - only on Linda clinic (I am not sure how to check whether they are assigned to another team)
@AnnieMungai Can you comment here the correct locations for the users? I assume the problem was inherited from OpenMRS (some edge case which we did not consider during the migration). I probably think the users were assigned to teams that later got deactivated or something..the import logic was just reading the data as in OpenMRS not doing any processing to determine whether the team is active or not - this is just my theory, I will look more into it.
@AnnieMungai the only way we can currently show which users is assigned to which team by looking are the team members on the team details sections.
We can however add the team assignment info on the user details sections. @rowo what do you think about this from a UX point of view.
@ellykits All the users are assigned the Linda clinic. As you mentioned this could be an issue with data that is compromised from OpenMRS.
@ellykits aall users at Linda clinic are having log-in issues - if they sync data, the app is crashing.
Let me check the logs in Crashlytics - are they using the latest app?
Indeed there are app crashes reported on Crashlytics. Some users are using devices running Android version 10. OpenSRP client apps are currently not compatible with versions 10 on wards. There are permissions issues that are still being addressed to avoid crashes with version 10 and above.
It appears the crashes reported (between May 31 and Jun 2) are for users using Android version 10. Total of 10 users affected with the exception of 1 using Android version 7 (with different logs)
@ellykits will this solve this issue? https://github.com/opensrp/opensrp-client-native-form/pull/491
Also why is the Android 7 device crashing also?
v.0.0.13 Will mark this as resolved and observe