When trying to identify the status of the email verification, I am using the following based on the iOS swift guide:

let user = Kinvey.sharedClient.activeUser

let status = user?.metadata?.emailVerification?.status

I am receiving the following error on the "emailVerification" method

'emailVerification' is inaccessible due to 'internal' protection level

Is there another module that I am needing to import besides Kinvey?  I'm confused why this is unavailable.

Thanks,

James

Hello James,

I have asked several questions regarding this problem of the engineering team. I will get back with you with more information and suggestions as soon as I hear back from them.

In the meantime, can you tell me which of your three apps is the one where you're experiencing this problem.

Which versions of Swift and our iOS SDK are you using?

Is this problem consistently reproducible or is it intermittent? I ask that because in our server logs show that you seem to be processing emailVerification requests successfully for one of your apps.

If you can reproduce the problem and provide the time, date and timezone of when you reproduced it along with some specific data identifying the request such as the email address of the user, that would also be helpful.

Regards,

Billy Gee

Kinvey, Inc.

Hello James,

We wanted to let you know that this problem has been fixed and should be available for download on or before the end of this week.

We will confirm when the download is available. Please let us know if you have any questions.

Regards,

Billy Gee

Kinvey Support

Hello James,

I am pleased to inform you that a new release of the iOS SDK v3.3.6 has been posted and is available for download at the following location.

http://devcenter.kinvey.com/ios/downloads

This update fixes the problem described in this ticket reporting the email verification error with Swift 3.

At your convenience, please download and test the fix and let us know if it works to your satisfaction.

Regards,

Regards,

Billy Gee

Kinvey Support

Hi Billy!

The new SDK has solved this issue.  Thank you and thanks to the Kinvey Engineers!

James