You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a aplication that pushes into the navigation stack diferrent pages, wich more than one has a CameraView to scan Barcodes. The problem occurs when i navigate back to a page that has a CameraView, it freezes. This only happen when i push more than 1 page with a CameraView and they are next to each other in the stack. I suspect it has something to do with the fact that the page i navigate back to it is not re instantiated, it is re used and the CameraView has some problem with that. This is the code of the page.
Sorry I currently don't have tome to test this properly but my guess is that when you go to second BarcodeView the Handler and underlying native Views from the first BarcodeView get disposed (DisconnectHandler() gets called) but the first BarcodeView doest not get disposed. So when you go back to the first BarcodeView you get the same instance but there is no Handler for it.
Try to to the same navigation just with BarcodeView.Handler?.DisconnectHandler(); commented out. If this works than you have a solution, you just need to find a more appropriate place to call DisconnectHandler() or do some check to see if the Handler needs to get disposed.
I have a aplication that pushes into the navigation stack diferrent pages, wich more than one has a CameraView to scan Barcodes. The problem occurs when i navigate back to a page that has a CameraView, it freezes. This only happen when i push more than 1 page with a CameraView and they are next to each other in the stack. I suspect it has something to do with the fact that the page i navigate back to it is not re instantiated, it is re used and the CameraView has some problem with that. This is the code of the page.
The text was updated successfully, but these errors were encountered: