Activities of "enisn"

Given your app crashes only in Release mode on physical iOS devices while functioning properly in Debug mode and simulator, this strongly suggests an issue tied to linker behavior, AOT compilation, or runtime entitlements, especially with regards to ABP's internal use of Secure Storage.

Here are our prioritized suggestions to further isolate and resolve the issue:

1. Revisit Linker Configuration Stick with the default linker setting: SdkOnly instead of None, as overly aggressive linker stripping can remove reflection-dependent services that ABP relies on.

If still unstable, try [Preserve] attributes or a linker descriptor (Linker.xml) for critical modules, especially those using reflection or DI-heavy services.

2. Verify Entitlements for Secure Storage MAUI apps read from secure storage in Release mode by default. Please ensure:

Entitlements.plist includes Keychain Access Groups.

In iOS Bundle Signing, Custom Entitlements points to your Entitlements.plist.

You’ve tested the SecureStorage sample independently in a Release build to validate your signing and entitlements pipeline.

3. Instrument for Logging Set up native crash logs using Xcode’s Devices & Simulators window after the crash.

Integrate a lightweight try-catch log writer for early startup to capture any fault at the MauiProgram.cs or DI registration level.

4. Build Environment Check You mentioned using VS Code on macOS — while building MAUI apps for iOS doesn’t strictly require full Visual Studio, the ABP tooling might assume certain project behaviors more aligned with VS for Mac. If possible, try compiling using Visual Studio for Mac to cross-validate.

Have you configured requirements for Secure Storage? MAUI app uses secure storage in Release mode to store tokens. Probably it tries to read auth token at the startup.

https://learn.microsoft.com/en-us/dotnet/maui/platform-integration/storage/secure-storage?view=net-maui-9.0&tabs=macios#get-started

That might be the problem, I cannot be sure about it, we need more logs to understand it

Since docs module is an open-source module, the issue can be tracked from here: https://github.com/abpframework/abp/issues/23012

It seems there is bug in the module, thanks for the reporting it. I'll deliver this issue to the team so they'll fix it

Hi, we identified that your Firefox version is 41.0.2, which is considered a legacy version. Due to this, some of our modern dependencies are incompatible with it, causing the issue you’re experiencing.

To resolve this, please update to the latest Firefox version, 139.0.1, and try again.

Hi,

I delivered this issue to our team and they could not reproduce this problem. Can you share use your environments like Firefox version, Operating System Build etc?

Also, check the followings thay can cause the problem on your browser:

• Browser Extensions– Sometimes, installed extensions (especially ad blockers or script blockers) interfere with site functionality. Ask them to disable all extensions temporarily and retry.

• Firefox Version – Ensure they’re using the latest stable version of Firefox. If not, they should update to the most recent release.

• Different Device – If possible, they should try accessing the website from another computer or mobile device with Firefox.

• Network Issues – Some ISP configurations or DNS settings can cause problems. Using a different network (e.g., mobile hotspot) could rule this out.

• Safe Mode Test – Running Firefox in Safe Mode (about:support → Restart with Add-ons Disabled) can help determine if an extension or setting is causing problems.

Hi again, I reached out to the ABP Suite team, and they clarified that ABP Suite generates code for a single UI—the main UI selected during project creation. However, if you create a module template, Suite can generate code for multiple UIs, but only within the module template.

So, the issue seems to stem from this design choice: ABP Suite is structured to generate code for the primary application UI, not additional UIs added manually later.

Hi,

We’ve successfully reproduced the problem and identified that it specifically affects Apple chipset Macs. Unfortunately, we haven’t found a solution just yet, our team is actively working on it.

Since this is a bug on our end, we’ll be refunding your ticket. We truly appreciate your patience and understanding as we work towards a fix.

If you have any further questions or concerns, please don’t hesitate to reach out. We're here to help!

Hi,

Thanks for reporting, It s working exctly what you described, we made an enhancement on TimeZones in ABP applications at v9.2.0 You can check this @maliming's article: https://abp.io/community/articles/developing-a-multitimezone-application-using-the-abp-framework-zk7fnrdq

This probably applies the logic what you need

Hi @yunusemrecaglar, Just to clarify—now that you've created a new Blazor Server project, has that resolved your issue, or do you still need assistance? Let us know how we can help.

Otherwise I can refund your ticket and close this issue since it was project generation problem on our side