Surface had no valid native window. on barcodeView.start()

[OmarJoya]

Surface had no valid native window. on barcodeView.start()

[alistairsykes]

We are yet to do a release with this fix in. We had a few other things to get done before publishing the code. I will post again on this issue once we have done that.

[alistairsykes]

Hi @OmarJoya . Thanks for reporting this, to clarify these are your steps to recreate:

• Be on Android 6 device
• Open app
• Request permission
• Once granted call barcode.start()

Is that correct?

[OmarJoya]

Yes, also I added the BarcodeView as an observer to the lifecycle in onActivityCreated as you have on https://github.com/brightec/KBarcode/wiki

[alistairsykes]

This exception does appear to be caused by affectively calling barcodeView.start() twice, in quick succession.

I had previously thought the library handled calling start() twice, as seen in BarcodeScanner.start() where I check if the cameraSource.isStarted(). However if you call twice in quick succession, the second time the camera source does not report as starting because it is still opening the camera.

I will create a pull request soon which will address this issue.

For your case @OmarJoya, you are right that marshmallow is the differing factor. It appears that permissions dialogs behave differently between M and Q (not sure exactly for each version in between). On M the permissions dialog causes @OnLifecycleEvent(Lifecycle.Event.ON_START) to be called when it dismisses. On Q it does not.
A temporary work around while I get this pull request together, would be to do a version check before calling barcodeView.start() after the permission is granted.

[alistairsykes]

Pull request has been approved and merged.

[OmarJoya]

does this last merge contain the fix?, I'm now using the kbarcode version 1.0.2, but seems the problem is not solved

[alistairsykes]

We have now done a release which includes this fix.

https://github.com/brightec/KBarcode/releases/tag/v1.0.3