-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SDK not working in an iOS credential provider extension #314
Comments
Hi @anmipo, would you be able to share a screenshot of the "Frameworks, Libraries, and Embedded Content" section under the "General" tab for the extension target's properties in Xcode? |
Thank you for looking into this, @Kyle-Reis. Here's the screenshot: I can make a demo project, if this helps. Also, not sure if relevant: I am testing the extension on unmanaged Safari. |
Hi @anmipo, So far everything with your config looks OK. A demo project would be great. Thanks! |
Are the intune frameworks supposed to be "Embed & Sign" instead of "Do Not Embed" |
@Kyle-Reis , it took longer than expected, but here's the demo project to illustrate the issue: https://github.com/anmipo/AppExDemo It's a barebones iOS app with a credential provider extension, both integrated with the Intune SDK. A user can successfully enroll in the main app, but that account is not visible to the extension. As a side note, @chasemac , the frameworks are indeed "Embed & Sign" for the app itself. The app extension, however, does not need to embed them — this would be unnecessary duplication. Instead, the extension links to the frameworks embedded in the parent app bundle. At least that's my understanding :) |
@Kyle-Reis , are there any updates, by any chance? Unfortunately, this is a blocking issue for me… |
Hi @anmipo - I did some digging into this and as it turns out, the SDK only supports s specific set of extension types, and that set currently does not include credential provider extensions. The list of currently supported extension types is: UI Action Extensions |
@Kyle-Reis, thank you for the response. Consider this a feature request then :) |
I struggle to get Intune SDK to work in a credential provider extension on iOS.
The SDK is successfully integrated both the in the main app and the extension:
IntuneMAMSwift.xcframework
andIntuneMAMSwiftStub.xcframework
are linked to both targets;The integrated Intune SDK works fine in the app itself: the user is prompted to enroll (MAM-WE), the app restarts, the APP are applied (the user is prompted to define a PIN), app config received, the user stays enrolled across restarts — everything works just fine.
However, the extension does not see any enrolled user, does not receive APP, and generally looks like Intune SDK does not do anything at all. I mean, my calls to the SDK work and return, so it's not a compilation/linking issue. But
IntuneMAMEnrollmentManager.instance().enrolledAccount()
just always returnsnil
.Am I missing something? Maybe there is a magic method to "activate" the SDK in the extension? Or the SDK is not supposed to work in AutoFill extensions at all?
Screenshots and logs:
Keychain sharing entitlement granted in both targets, with the following config in both
.entitlements
files:Shared app group container configured in entitlements for both targets:
Here are the Intune settings section of extensions'
Info.plist
:The extension has access to the app group container (can write/read files there). It also has the access to the keychain group, here's the list of items the extension sees in the keychain:
Keychain contents as seen by the extension
Here are the log files returned by
IntuneMAMDiagnosticConsole
(called from the extension): https://gist.github.com/anmipo/f6581e269a2eacef057280128130777fRemarkably,
Intune-com.myapp.intune-0.txt
does not even mention extension's bundle ID (com.myapp.intune.AutoFill
)Smartphone:
Intune App SDK for iOS:
The text was updated successfully, but these errors were encountered: