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

[BUG] Problems with barcode scanning and data collection #487

Closed
Minaella opened this issue Aug 10, 2022 · 4 comments
Closed

[BUG] Problems with barcode scanning and data collection #487

Minaella opened this issue Aug 10, 2022 · 4 comments
Labels

Comments

@Minaella
Copy link

Describe the bug
I transferred data (Field Book apps, files) from Galaxy Tab A7 Lite to another via Smart Switch (I've done it before with other tablets and everything works). When I tried to use the new A7 it crashes every time I try to scan a barcode it shuts down, after that I can't collect any more data, every time I go to collect , it closes instantly.

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'Collect'
  2. Field book closes

Expected behavior
Be able to scan the barcode and go directly to the desired plot and collect data

Screenshots
If applicable, add screenshots to help explain your problem.

Device Info (please complete the following information):

  • Model: Galaxy Tab A7 Lite
  • OS:
  • Field Book Version 5.2.5

Additional context
Add any other context about the problem here.

@Minaella Minaella added the bug label Aug 10, 2022
@trife
Copy link
Member

trife commented Aug 19, 2022

Hi @Minaella
I think this issue will be fixed in 5.3. Until then, if you export the database (Settings > Database) from your old tablet and import it into the new tablet, are you able to use Field Book?

@Minaella
Copy link
Author

Minaella commented Aug 24, 2022 via email

@trife
Copy link
Member

trife commented Aug 29, 2022

If you upload or email me the file I can check it out to see what the issue is. We don't have a set deadline on v5.3 but will hopefully have a beta out soon.

@trife
Copy link
Member

trife commented Sep 1, 2022

Closing this for now. If this issue reoccurs in 5.3 it can be reopened.

@trife trife closed this as completed Sep 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants