The compliance audit angle is smart - Apple's review guidelines are long and the edge cases aren't always obvious until you get a rejection. Does it catch things like missing privacy manifest entries or is it focused more on the metadata and listing side?
Report
Maker
@liviu_chita We are uploading our app bundle to check all policy done by micro verifying low level files pulled out from the bundle. Its a Opensource Project for a reason - To make all edge cases solved. Is this doing now ? - NO
So , whats its onto now ?? - It checks mostly info.plist(manifest entries), app delegate.swift, .swift files, other generated.
@athrvnaik7 good to know on the info.plist and Swift file coverage - that's actually where most of the painful rejections hide. will keep an eye on the repo as the edge cases get added
Report
Maker
@liviu_chita yes we are working with all even security compliances will be covered soon
Replies
Github to ⭐ :: https://github.com/atharvnaik1/GraciasAi-Appstore-Policy-Auditor-Opensource
Product Hunt to Upvote 🔼:: https://www.producthunt.com/products/gracias-ai-opensource
Product link 🔗 :: https://opensource.gracias.sh
medium Company blog 📰 :: https://medium.com/@gracias.sh
Linkedin : https://www.linkedin.com/company/gracias-ai/.
The compliance audit angle is smart - Apple's review guidelines are long and the edge cases aren't always obvious until you get a rejection. Does it catch things like missing privacy manifest entries or is it focused more on the metadata and listing side?
@liviu_chita We are uploading our app bundle to check all policy done by micro verifying low level files pulled out from the bundle. Its a Opensource Project for a reason - To make all edge cases solved. Is this doing now ? - NO
So , whats its onto now ?? - It checks mostly info.plist(manifest entries), app delegate.swift, .swift files, other generated.
We encourage you to pull our code in your machine https://github.com/atharvnaik1/GraciasAi-Appstore-Policy-Auditor-Opensource ( to setup our dev team will help you - reach at atharv.naik@gracias.sh ) and try adding some extra edge cases in our github repo as in ISSUES or suggestions.
Thanks.
@athrvnaik7 good to know on the info.plist and Swift file coverage - that's actually where most of the painful rejections hide. will keep an eye on the repo as the edge cases get added