Semantic Issue in SafeDeviceJailbreakDetection.m not allowing the app to launch in iOS from Xcode(16+).

[bibekpandainnopay]

After the latest release 1.3.9+ facing the semantic issue in SafeDeviceJailbreakDetection.m file for Xcode(16+) which is not allowing the app to launch on iOS devices/simulator because variable jailbreakVarPaths in SafeDeviceJailbreakDetection.m were declared as static ... const (file-scope constants) but were assigned in an Objective-C array literal @[...], which is not a compile-time constant in C/Objective-C which Xcode 16+ enforces. Have added the fix. Can I raise a PR for that?

[ufukhawk]

Hi @bibekpandainnopay 👋

You're absolutely right — this is a genuine Xcode 16+ compatibility issue. The @[...] Objective-C array literals are runtime objects, not compile-time constants, so Xcode 16+'s stricter Clang enforcement correctly rejects them as static const file-scope initializers.

#99

Both jailbreakVarPaths and jailbreakNonVarPaths have been converted from file-scope static const variables to class methods using dispatch_once for lazy initialization — consistent with the existing jailbreakPaths and jailbreakSchemes methods in the same file.

Before (❌ Xcode 16+ error):

static NSArray<NSString *> * const jailbreakVarPaths = @[ ... ];
After (✅ Fixed):

• (NSArray<NSString *> *)jailbreakVarPaths {
  static NSArray<NSString *> *paths = nil;
  static dispatch_once_t onceToken;
  dispatch_once(&onceToken, ^{
  paths = @[ ... ];
  });
  return paths;
  }
  A PR will be raised shortly. Thank you for raising this!

If you still think there is a problem, please let us know.

[bibekpandainnopay]

I did check by adding this fix locally and it was working. Thanks for resolving it. Will wait for it to merge to master.

[kjust-extron]

@ufukhawk Hi there. Is there an ETA on when the open PR for this issue will be merged and a new package published? My company uses this package in one of our projects, and this error has become a blocker.

[ufukhawk]

In line with this PR effort, the error has already been resolved. @kjust-extron