Highlighted
Contributor
Contributor

iOS 13 Devices Marked as Compromised

Hey All,

Curious if anyone has any folks already upgrading to iOS 13 and if they are seeing any issues with devices being marked as compromised. We have 9 developers that have upgraded for testing and 3 of the 9 have been marked as compromised after upgrading but 6 of them seem to be fine. I'm guessing something is going a little weird during the update process that confuses Intelligent Hub but was curious if anyone else is seeing odd behavior.
Labels (1)
100 Replies
Highlighted
Contributor
Contributor

thank you.  the latest app wrapping engine?  would there be a specific place to check this?
0 Kudos
Highlighted
Enthusiast
Enthusiast

If you scroll down to the apps section this will tell you the version it needs https://kb.vmware.com/s/article/2960338?lang=en_US&queryTerm=2960338 they seem to keep updating the version without sending a notice though so keep an eye on it
0 Kudos
Highlighted
Contributor
Contributor

Great thank you.  I will have to have our server admin take a look at the tunnel version to see if it meets the requirement.  I am guessing we will need to disable compromise protection for the time being.
0 Kudos
Highlighted
Enthusiast
Enthusiast

You will also want to verify the sdk version in that list
0 Kudos
Highlighted
Enthusiast
Enthusiast

I have case opened with Engineering support team on Device Assigned purchased VPP app for Agent Intelligent Hub not updating to 19.08 shows 19.07.  Need 19.08 to keep devices from reporting compromised. I have remote wipe set to disable, since last upgrade when I had a bunch of devices remote wiping due to Agent app was not up to date.
0 Kudos
Highlighted
Contributor
Contributor

Is anyone experiencing issues opening attachments with Content after updating to iOS 13?
0 Kudos
Highlighted
Contributor
Contributor

We are getting devices showing up as compromised when our users upgrade to IOS 13 and above.  They are all reporting that their Hub app is at 19.08.
0 Kudos
Highlighted
Enthusiast
Enthusiast

If you have internally developed apps with an older AW SDK, that will flag your device as compromised.
0 Kudos
Highlighted
Enthusiast
Enthusiast

We do not have any wrapped or sdk using internal apps here just the AirWatch apps set to auto update and we are getting false compromises.  There are also seems to be no supported version for most of the apps for iPad OS per their chart
0 Kudos
Highlighted
Contributor
Contributor

I have one iOS 13 device the randomly becomes compromised.... then doesn't. Strange thing is this device was previously used to test iOS 13 during the summer beta period however it's running stable release code now.


update:  installed ios13.2 beta 1 and device is no longer compromised.

0 Kudos
Highlighted
Contributor
Contributor

iPadOS 13.2 Public Beta is declared as ' compromised'  in our enviroment (WSONE 19.03)
A new update is currently not available.


update: Only our iPad Pro 11'  will be displayed as ' compromised'  and an Enterprise Wipe will only be executed when I start the Hub App.
Our iPad Pro 9,7'  is not affected, other iPads have not yet been tested.

0 Kudos
Highlighted
Contributor
Contributor

Chiming in on this issue. I've a user who installed the iOS 13.2 (17B5068e) update and his phone is now detected as compromised.
0 Kudos
Highlighted
Enthusiast
Enthusiast

Can confirm iOS 13.2 beta 2 (17B5068e) is detected as compromised.
0 Kudos
Highlighted
Enthusiast
Enthusiast

I have an iPad running iOS 13.1. I just discovered that the native Apple ' Files'  app has the ability to connect to files shares using SMB. When I configured it to connect to a file share, it completed successfully. However, as soon as I launched Boxer, it was detected as being jailbroken and wiped. This happened to another user as well who configured it to connect to a share on a file server.
0 Kudos
Highlighted
Contributor
Contributor

same thing here on a Iphone XR, as soon as I went to ios 13.2 public beta 2 it went to compromised
0 Kudos
Highlighted
Contributor
Contributor

I have iPhone 11 Pro, 13.2 Beta and Hub 19.09.1 and it is being marked as compromised.
0 Kudos
Highlighted
Contributor
Contributor

After 4 days of sitting as compromised on iOS 13.2 beta 2 the device is no longer listed as compromised. 

Magic
0 Kudos
Highlighted
Enthusiast
Enthusiast

The problem doesn't seem to occour on iPad Pro 11inch 13.2 beta 2 (17B5059g).
0 Kudos
Highlighted
Contributor
Contributor

AW updated the AppWrapping Engine to support iOS 13 a week and half ago or so.  Since then our issues marking as compromised have subsided.  13.1.2 & 13.1.3 devices seem to be marked as compliant for now.
0 Kudos
Highlighted
Contributor
Contributor

I had one user upgrade to iOS 13 and they had old versions of boxer and hub.  This triggered the device as being non-compliant.  The user has updated both hub and boxer but the device is still flagged as out of compliance?  Any way to remedy this?  Support had recommended a full device wipe however this is a very poor solution.
0 Kudos