It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption to this rule, contact Hixie on the #hackers channel in Chat (don't just cc him here, he won't see it! He's on Discord!).

If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix?

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing.

I think since this is just a temporary flag to help with debugging flutter/flutter#100522, this is okay, but in general a flag like this should be parsed along with the others in shell/platform/darwin/ios/framework/Source/FlutterDartProject.mm, and plumbed through e.g. the IOSContext object.

hey @chinmaygarde , couple of things:

1. The issue seems to indicate that this is only happening on iOS, so I limited this to iOS.
2. If this were a more permanent fix, I'd have wired it through IOSContext, as this is temporary to see if it helps with the problem at all, I ended up resorting to directly calling [NSBundle mainBundle], we are doing this at other places as well, for ex: platform views.

If this does indeed resolve the issue, I think we should think about a more long-term fix, maybe consider disabling DRM for all devices, or maybe focus a more involved effort in root-causing issues with DRM on iOS devices, but I'd really like to revert this if it doesn't prove to be a fix long term. Let me know if you disagree.

Sound good! I LGTM'ed already.