star-micronics / StarPRNT-SDK-iOS-Swift

StarPRNT SDK for iOS including libraries for supporting application development for Star printers.
https://www.star-m.jp/products/s_print/sdk/starprnt_sdk/manual/ios_swift/en/index.html
Other
41 stars 7 forks source link

[BUG] App built with Xcode 14 causes crash when calling disconnect #21

Closed monolithic-adam closed 1 year ago

monolithic-adam commented 1 year ago

Description

A clear and concise description of what a bug is. disconnect

Your device where the bug occurs

Your printer

Your development environment

The result of executing the command ver on Windows, sw_vers on macOS, uname –a on Linux, or these equivalent commands. ProductName: macOS ProductVersion: 12.5.1 BuildVersion: 21G83

To Reproduce

Steps to reproduce the behavior:

  1. Call disconnect on StarIoExtManager

Expected behavior

A clear and concise description of what you expected to happen. not crash

Screenshots

If applicable, add screenshots to help explain your problem. N/A

Additional context

Add any other context about the bug here. Crash Title on Firebase

-[StarIoExtManager .cxx_destruct]
EXC_BREAKPOINT
StarIoExtManager.m:71

Crash Log

3
POS
StarIoExtManager.m - 行 53
-[StarIoExtManager .cxx_destruct] + 53
4
libobjc.A.dylib
object_cxxDestructFromClass(objc_object*, objc_class*) + 116
6
libobjc.A.dylib
_objc_rootDealloc + 80
7
POS
StarIoExtManager.m - 行 121
-[StarIoExtManager dealloc] + 121

Crash Key Log

BUG IN CLIENT OF LIBDISPATCH: Semaphore object deallocated while in use

Happens about 44% while the app is in the background (with background operations on) Edit: now happens around 76% in the BG

gare-bear commented 1 year ago

@monolithic-adam Looking into it.

gare-bear commented 1 year ago

@monolithic-adam I've compiled a bunch of apps since you opened this issue, and I haven't reprodued any crashes. Does this happen with the sample app? Or just your own app?

gare-bear commented 1 year ago

@monolithic-adam i'm going to close this issue for now, but if you are still having this issue, we can re-open it.

monolithic-adam commented 1 year ago

@gare-bear Sorry I couldn't answer sooner, we got busy on another feature's development and this crash got put on the backburner, we are still having this issue in our app but I haven't tried the sample app because tbh we cannot reproduce it when testing, we are getting alot of crash reports on Firebase for it and were hoping that others were facing the same issue.

monolithic-adam commented 1 year ago

@gare-bear I edited the Issue to give it a bit more detail in the Issue description, the symbolicated crash has to do with a semaphore that was deallocated while in use. I hope it helps a little!