Seb Jachec

For the time being, right-click `Sketch Constraints.sketchplugin`, click `Show Package Contents` then go to `Contents/Sketch/manifest.json` and change line 14 if you want.

Seeing the same issue with a similar schema file format here, comparing local JSON schema against an endpoint.

Agreed! We recently migrated over from Cocoapods to Swift Package Manager + a shared framework in our KMM project, so the failing Cocoapods check is misleading & irrelevant to us.

@dos9191 Couldn't figure out what was going on – took a quick route around the problem to get AltStore up and running instead. If I remember rightly, I compiled &...

@manijak I'm not really sure what was going on for me before unfortunately – I can no longer reproduce the installer crash I was having. The pre-built AltServer app (version...

@PavloZoria @NielsMasdorp Were either of you able to implement this in the end? I'm looking at something similar, with a horizontal pager of items in Jetpack Compose, each backed by...

Using `KeychainSettings` in a project at the moment, providing a couple extra default properties (`kSecAttrAccessible` & `kSecAttrAccessGroup`) – seems to be working well, haven't found any issues (will update if...

Hi @rizafran, * This is the first time I've set `FirebaseAppDelegateProxyEnabled` to `false` and then submitted, giving the warning * A previous build without the key `FirebaseAppDelegateProxyEnabled` had the same...

I suspect the warning may be an issue with Apple's analysis tools, as breakpointing inside both `GULAppDelegateSwizzler` and `GULSceneDelegateSwizzler` seems to show the Firebase SDK is reading `FirebaseAppDelegateProxyEnabled` as expected...

@chliangGoogle Yes, the issue still exists for me unfortunately – still getting the same email from Apple each time a new build is submitted.