We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When trying to connect and print our react native app crashes with the following error caught.
NSInternalInconsistencyExceptionfacebook::react::JSIExecutor::defaultTimeoutInvoker(std::__1::function<void ()> const&, std::__1::function<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > ()>) Invalid parameter not satisfying: characteristic != nil
Seems that characteristic != nil is not caught/handled correctly.
characteristic != nil
RNZebraBluetoothPrinter.connectDevice(this.state.zebra_printer.address) .then((result) => { if (!result) { Alert.alert('Could not connect to printer. Please check printer connection.') } RNZebraBluetoothPrinter.print(zpl) .then((result) => { if (!result) { Alert.alert('Printing failed. Please check printer connection.') } }) .catch(e => console.log(e.message)) }) .catch(e => console.log(e))
The text was updated successfully, but these errors were encountered:
Seeing the same issue on iOS 14. Were you able to find a workaround?
Sorry, something went wrong.
For me it helped to implement a brief timeout between the methods connectDevice and print. Just a workaround - not a solution for the root problem.
connectDevice
print
await RNZebraBluetoothPrinter.connectDevice(printerSerial) .then(() => { new Promise((res) => setTimeout(() => res(true), 500)) .then(async () => { await RNZebraBluetoothPrinter.print(zpl) }) })
hi could u solve? I cant print on ios
No branches or pull requests
When trying to connect and print our react native app crashes with the following error caught.
Seems that
characteristic != nil
is not caught/handled correctly.The text was updated successfully, but these errors were encountered: