[Solved] Scan not working at all

Bug reports
1

Hi, I’ve had this issue for quite awhile now, the scan function is not working at all. I select the photos I want to scan, and then it just hangs and never moves to the next step. I’m on Android, version 15, Pixel 7a. Never done a bug report before, so please let me know if you need more info.

1 Like
2

Closing and opening the new window helped me. It would get stuck loading, on new window everything worked fine

3

Thanks for the suggestion, unfortunately it didn’t work. :cry:

4

I have not checked if it works for me, but I just uploaded a picture of the error that I get.

I was not aware that I was not alone in this issue.

2 Likes
5

I realized that there is a thread on Github about this issue, so it is under revision. But collective help and more evidence could help devs to figue out where is the problem.

1 Like
6

Ya same for me for about 4 or 5 days I think - scan takes a long time to initialize and then I get the error after hitting the ‘update selected cards’ button.

1000018990
10000189901344×2992 210 KB

1 Like
7

Bugfixe has just been pushed, let me know if this works for you.

8

I just tested and still getting the error

9

Could you make a screenshot of the error?

10

Here you go

IMG_2587
IMG_25871320×2868 245 KB

11

Just tested and single screenshots of single cards are working, but bulk images of more than 1 card wasn’t

12

Thanks! Seems a different error then earlier reported and was fixed. I’ll take a look.
Any tips on how to reproduce this?

13

Same for me. Still getting the error with multiple cards but image of a single card worked.

1000018994
10000189941344×2992 257 KB

14

are these cards you already own or new cards?

15

I can’t reproduce this issue at all unfortunately.
If any of you can reproduce this on a computer and look at the dev console of the browser (right click → inspect → switch to console tab), then send me the error (if any). That would be very helpful.

17

New cards from packs I’ve been opening over the last week or so. I can’t remember if it started before or after the new eevee pack was released…

18

It doesn’t make sense that some people get this error. Must be some quirk with supabase. I’ve set the created_at column to optional for now. That should remove the error. Can you validate and let me know if that makes a difference?

1 Like
19

I have successfully scanned 72 cards, thank you so much!

20

Yup me too just scanned 30 cards :slight_smile:

21

I scanned 10 successfully! I do have to try to scan, then cancel, then scan again for it to work, but at least it works :joy: