QR Generator Factory 5 4+

For some reasons my review dissapeared. Since 5.7.0 it crashes on launch.
This app is not a proper mac app (escape key/enter doesn't work to dismiss panels etc), dragging image doesn't work to desktop/download folder only to other apps. CMYK is with retargetting from RGB to you won't get proper black color. Developer did not try to select color from other color palettes on the color picker. On top it's being released almost daily with numerous bugs. You can see version changes. This app should be considered as beta as it's not stable. It crashes for me since version 5.7.0 On top is ultra slow and the QR codes cannot be scanned with cheaper dumb phones.

Each setting window can now be dismissed with escape since multiple versions ago, CMYK colors can now be selected from the color pickers due to a big rework on how we store color values and now you can have absolute black on the bitmap exports, we had a big performance update in 5.7.5 which should resolve your slow concerns. QR's vary, it all depends on how much content you use, what colors you use how big the logo is (how many pixels are obsured) - If you are using a long URL we would suggest using our dynamic QR option to reduce the size of the QR, we'd suggest being careful with logo sizes and colors (i.e not having fill colors too similar to background colors for example). The built in verifier is fussy so it will often say not verified when a multitude of high end phones will still be able to scan it, as it verifies with all devices in mind.

The drag option is intended for dragging into other applications - however after considering your feedback we have decided to implement this feature and it will be in the next version:)

If you would mind sending a crash report to contact[at]runecats.com we can take a look, we have also had one other user with a crashing issue so maybe they are related.

Was working great one week ago and now crashes on launch.

Sorry to hear it's started crashing for you, please let us know if the crashing issue is now resolved for you, and if it is we hope you can adjust your review in time to reflect how the app is now! If it still an issue for you then please send a crash report to contact[at]runecats.com so we can rectify this issue as quickly as possible!

The crash report you provided is for the "QR Generator Factory" application (version 5.3.8, build version 6.0.10) on a macOS 14.2.1 system. The application crashed due to a SIGABRT signal, which is typically an indication that the application itself has detected an anomaly and terminated deliberately.

Key points from the crash report:

- **Crashed Thread**: The crash occurred in the main thread (thread 0).
- **Exception Type**: SIGABRT, which usually indicates that the application has triggered an abort signal to itself, often due to internal errors or failed assertions.
- **Application Specific Information**: The report specifically mentions `abort() called`. This suggests that the application decided to terminate itself due to an unhandled exception or serious issue.
- **Stack Trace Analysis**: The stack trace for the main thread shows the sequence of calls leading to the crash. It appears the crash happened during a UI operation (likely related to setting a value on an NSTextField).

A closer look at the stack trace reveals the following sequence:

1. A setter method (`setStringValue:`) is called on an NSTextField object.
2. This leads to an assertion failure within the AppKit framework.
3. The application terminates due to this failure.

To resolve this issue:

1. **Code Review**: Review the part of your code that interacts with NSTextField, particularly where `setStringValue:` is called. Ensure the value being set is valid and the NSTextField is properly initialized and not nil.

2. **Exception Handling**: Implement proper exception handling around the code that's causing the crash. This can prevent the entire application from crashing due to issues with a single component.

3. **Debugging**: Run the application in a debug environment and reproduce the crash to get more detailed logs or to inspect the application state at the time of the crash.

4. **Update Check**: Ensure that both the macOS and the application are updated to their latest versions, as updates often include bug fixes.

5. **Contact Developer Support**: If you're unable to resolve the issue, consider contacting the developer of the "QR Generator Factory" for support, especially if it's a third-party application. The crash might be due to an internal bug in the application.

6. **System Check**: Since the crash report includes a lot of system information, make sure that there are no system-level issues contributing to the crash. This includes checking for sufficient memory and storage, as well as scanning for any system file corruption.

We've been making some big under-the-hood changes, look out for 5.3.9 which is awaiting approval from Apple which should hopefully resolve your issue. We appreciate your patience while we've been working on this.