App Tracking Transparency Permission can't be set on iOS

[jacobsapps]

Hello 👋

I'm fairly new to Maestro and absolutely loving it. Transitioning to this from Appium is like the difference between ARM Assembly and SwiftUI. Simply 🤯.

I've got a small teething issue which I think might be a bug on Maestro's side.

I can't set App Tracking Transparency permissions state in my flows.

I'd expect to set it as such:

appId: my.app.id
---
- launchApp:
    clearState: true
    permissions:
        usertracking: unset
- runFlow: subflows/my-subflow.yaml

I have some navigation logic which shows my ATT permissions screen if ATT is not yet set, but this does not show up when running these tests. However, when deleting the app from Simulator and running a real fresh install, the screen does show up. Therefore, it seems like the ATT permissions aren't being set via launchApp.

I've looked in your source code and in maestro-ios/src/main/java/ios/simctl/Simctl.kt the usertracking permission is listed in the list of all permissions, but it seems like it's not actually applied.

Would really appreciate any help you can give, and happy to share more info as required!

Thanks,

Jacob

[ArthurSav]

Hi @jacobsapps thanks for reporting this issue. We'll take a look.

[aldo-astro]

I think it's already added in LocalSimulatorUtils.kt about 2 months ago.

Since I have a similar use case, I'll verify the flow that uses app tracking transparency in my simulators, I hope this issue has been resolved 👍

[otoniel-isidoro]

seems that the notifications permission is missing for ios too. Why the notifications permission is not listed here? https://github.com/mobile-dev-inc/maestro/blob/8aacc071649fe0b5eb755d6fe92ea115245d1a63/maestro-ios-driver/src/main/kotlin/util/LocalSimulatorUtils.kt#L345C5-L345C5

[bartekpacia]

Thanks for reporting (and sorry about the problem, of course). If someone would like to take a stab at it, we are happy to receive contributions and will do our best to review them promptly.

[Fishbowler]

I believe this was fixed in #1476.
Annoyingly, I suspect you need to use userTracking - case sensitive :(