microsoftconnect / Chatr-Sample-Intune-iOS-App

Chatr is a simple, open source, Swift based iOS app designed to let you test out the capabilities of the Microsoft Intune APP SDK
MIT License
10 stars 5 forks source link

Unable to sign in - the user is not licensed for MAM #52

Closed hank345 closed 4 years ago

hank345 commented 4 years ago

Hi,

I signed up for an Intunes trial licence (30 days), and now I'm trying to run this example app but the authentication does not seem to work. I'm getting this error message: "The operation could not be completed because the user is not licensed for MAM."

The error occurs after this is called in the LoginPage: IntuneMAMEnrollmentManager.instance().loginAndEnrollAccount(nil)

I double checked in the Microsoft Endpoint Manager Endpoint manager, and the user indeed has an Intune license. Do you know what else can cause that error message?

Thanks,

Henrik

hank345 commented 4 years ago

Ok, my bad. For some reason I missed issue #51. I will try to perform the steps suggested there, and let you know if that works. Kind of a misleading error message though?

Kyle-Reis commented 4 years ago

Hi @hank345, the root cause of issue 51 is actually a bug in the Intune SDK which we are addressing. There is a simpler work around for it though. But first, I just want to make sure this is the same issue. Are you being prompted for credentials when loginAndEnrollAccount is called? If not, is this a device with which you tested Intune with in the past using a different account that may no longer exist or be licensed for Intune?

hank345 commented 4 years ago

Hi Kyle, For some reason today, it actually started working. Now the problem is that I'm not exactly sure why :/

But earlier, yes I was prompted for credentials. I'm on a 30 day trial at the moment. Since I started testing the user I'm using has always had a license. I first started with my own app based on what I could find in the documentation, but then switched to your example (with the same user). The difference between the apps was that my first test app tried to call loginAndEnrollAccount with the e-mail of my previously signed in user.

I'm sorry I could not give more specific details.

parveen-bhatia commented 3 years ago

I am facing same issue. Authentication using MSAL (1.1.17) works fine. But getting error on enrollment with intune using loginAndEnrollAccount. Enrollment is working fine after reseting the iOS simulator. But it's hard for users to reset the device.

@Kyle-Reis can you please suggest any workaround or do you know in which version it would be fixed.

msft-neiljac commented 3 years ago

Hi @parveen-bhatia. Can you describe the issue you are seeing?

Thanks, Neil

parveen-bhatia commented 3 years ago

@neiljac1 this is the same issue posted in this thread.

I am able to authenticate using MSAL (1.1.17). But enrollment with intune sdk using loginAndEnrollAccount is failing with this error: "The operation could not be completed because the user is not licensed for MAM."

Although i verified user has the license and on reset on simulator enrollment works fine also.

msft-neiljac commented 3 years ago

Hi @parveen-bhatia,

Can you try setting IntuneAutoUnenrollEnabled boolean to 1 in NSUserDefaults before calling loginAndEnrollAccount? This will give you the option of specifying the account to log into rather than loginAndEnrollAccount picking up the previous account.

Thanks, Neil

kapilntt commented 2 years ago

Hi,

I am also having the same problem and resetting simulator is not helping either. Details as follows:

The setup:

This is what user actions and observes:

What I have tried so far but didn't help

Please let me know if I have to report this as a new issue.

SameerK-MSFT commented 2 years ago

I am having the same issue.

thomasarogers commented 4 months ago

Anyone resolved this since?

lukeashton4 commented 3 months ago

I am facing the same issue here too.

lukeashton4 commented 1 month ago

@Kyle-Reis @msft-neiljac Can this be re-opened or should I open a new support case? It looks like lots of people are encountering the same problem. Thanks