Open eboehnisch opened 3 years ago
The warning stems from the TextExpander framework's use of [UIApplication sharedApplication] in a few instances. Two examples are: an openURL call to the TextExpander app to get the current snippets and an openURL to the TextExpander app in the event the user expands a snippet with fill-in content. I don't think we could avoid this warning without building a separate framework for application extensions. I'm also a bit unsure of whether extensions have access to their host application's instance of the TextExpander data. Feel free to follow up with me via email if you'd like to discuss your use case privately.
When embedding the framework into a share extension we get the following warning:
Is the TextExpander framework safe for embedding into extensions, and if yes, could it be built so that it doesn't throw this warning?