BarcodeScanner | Official repository now at [ | Plugin library

Keep in mind, batch can't interpret .json files and handles them as pure text. So any batch solution will highly depend on the exact format of the file. Any change in the format (a stray space might be enough) may cause trash.

That said: use a flag that changes at (each) line that starts with "plugins": and changes back when hitting the line starting with } (end of the block) and write the line dependent on the flag:

Figured out what the issue was. MicrosoftSDK had TypeScript 3.1 and first when running "where tsc". I moved the npm directory up in the Environmental Variables. Then I removed Angular and reinstalled it.

mark these two options in debug menu, you'll see a red screen on your device/emulator, that's what the problem is. Try to solve the issue.

if that's not working try to run app in release mode by running the following command:

flutter run --release -v and see the result in terminal in VS code

We could pass the barcodeData back to the HomeScreen using route params. Actually, from the code that you have provided, we could remove the state in BarcodeScanner and pass data in the handleBarCodeScanned function directly.

This could be implemented as follows. I assume that HomeScreen is a Screen defined in a navigator.

You have an incorrect mock for onScan and you are not waiting for results. The action is resolved in the next "tick" not instantly. I think this should work (not tested)

It is a design choice. It is not necessary for any view to have a view model to function. However, Google recommends the pattern because it leads to good design.

If you want to say that your app is MVVM, then you need to keep the view separated from the data that drives it. This typically requires a translation layer to query and transform the model data in to data that can be consumed by the view.

I didn't read this article thoroughly, but it has a diagram that illustrates the relationship between the model, view model, and view:

https://www.journaldev.com/20292/android-mvvm-design-pattern

In your barcode scanner button example, the API server can be thought of as the model. Your view model should interface with the API (make the GET calls) in such a way that it can post updates to the view (typically using LiveData). The view stays up to date by observing the API results.

I would recommend isolating the interface to the API in it's own class or service. Then the view calls the view model when the barcode scanner button is clicked and the view model call the API class.

Regarding your bundle populated details page question: It's hard to know without looking at your code, but presumably your main activity is populated from data in a database (whether local, or through an API). You recycler view contains a list of items, and upon selecting an item, it's details are displayed in a new view. If I were implementing that, I would pass only the ID of the item to the detail view and initialize the view model with that same ID. Then the view model would lookup all data associated with the item and display it.

Presumably more data is displayed in the detail view than in the RecyclerView. The main activity does not need to access the item details or hold them in a ViewAdapter (and should not).

However, these are all design choices. There is nothing that says your app has to be written a certain way or follow a certain pattern. It can function regardless. My advice is to follow the pattern even when you think you don't need to until you learn why you need to!

I found a workaround for the Problem. The App has a SplashScreen on start and I simply set the state of canGoBack to false and am clearing the WebViews history when the SplashScreen closes.

How about toggling some kind of waiting period while the data is actually getting sent to your server via the POST in a synchronous matter to stop the scan and then reactivate it right after?

I don't have the chance to test it on an actual device and replicate it to the precise bit but I hope you'll get the gist of it:

Welcome @Backup Gov18,

This is a documented issue.

Note: Only one active BarCodeScanner preview is supported currently. When using navigation, the best practice is to unmount any previously rendered BarCodeScanner component so the following screens can use without issues.

There is a workaround.

Instead of conditionally rendering the component, you could render it inside another dedicated screen component.

This way, after this new screen reads the barcode, you could navigate back to your first screen. Navigating back may unmount this new screen. You can force unmount if you need to.

As you are using react-navigation, you had better use .pop() instead of goBack().

You can also use expo-camera instead of expo-barcode-scanner. expo-camera does not have this issue. It also offers more options like flashlight/torch and switching cameras.