ksinas

I have the same issue, when I try to update users collection `profile.name` field. We have an extra property `title` and if you remove it, there is no update coming...

Actually, the problem is with Meteor.defer. I replicated it and wrote a simple app which shows the sequence of actions. You can see that they are called in different sequence...

What if something like this? If we avoid stopping initial computation, then we would also preserve the same output from the first computation. Is there any negative consequence to this...

I wouldn't change it to setTimeout. You could just always stop the computation on the start of the useEffect. But how about my previous suggestion? It solves 2 issues instead.

I'm not exactly sure how concurrent mode works under the hood, but I would be surprised that it would evaluate useMemo multiple times with the same deps. That sounds like...

> It definitely does - useMemo is just run inline with the rest of the render, and if the render is suspended, it's values are discarded. (I've seen some assertions...

> I wouldn't change it to setTimeout. You could just always stop the computation on the start of the useEffect. That's the same solution I proposed earlier. Will we see...

~I also have the same `Scanner error: timeout` issue. Worker is loaded correctly. Tested on MacOS Safari~ My mistake, my packaging system wrapped qr-scanner-worker.min.js file in a function, which was...

> I have the same error on my iPhone, on my MacBook Air m1, it works fine with firefox though: > Scanner error: timeout You need to make sure the...