Switching to Xcode 13 we got an issue in one of our unit-tests checking the proper conversion from JSON to our object model. In our json we have some money value amounts like "{"amount": 90.21 }". Until now we parsed them as Decimal without any issues. But now, we don't get a Decimal 90.21 anymore, we get Decimal 90.20999999... This is reproducable only with iOS 15 Devices and values between 64 and 99 with 21 after the decimal point. It looks like there is a conversion to double in between or so?

We noticed that we don't get any code coverage anymore since upgrading. running Xcode 14.1 on macOS Monterey 12.6.1. digging through the build logs, I found this warning: Failed to generate coverage for target XYZ.app at paths (    "/Users/ME/Library/Developer/Xcode/DerivedData/XYZ-gxxobnuibhmtifdnkgfomguzzhnv/Build/Products/Testing-iphonesimulator/XYZ.app/XYZ" ): malformed instrumentation profile data. (Underlying Error: malformed instrumentation profile data) Anyone else had this since upgrading Xcode? We tried different machines, settings, new testplans, other tests, same results.

Hi community, my existing ui-tests did test push-notification interactions. Since upgrading to Xcode 13 those tests fail when tapping a by the generic tap via XCUIApplication(bundleIdentifier: "com.apple.springboard").otherElements["Notification"].firstMatch.tap() this is the error I get *** -[__NSArrayM insertObject:atIndex:]: object cannot be nil (NSInvalidArgumentException) actually the push notification is visible and can be queried in the debug console. just tapping it, crashes the test. I`m testing this with a real device (iPhone X, iOS 15). Testing on a iOS 14 device still works. Did anyone else face this problem or solve it? Thanks you

Since upgrading to Xcode 13.3.1 unit-tests doesn't start anymore with "execute in parallel" set on. "XYZ" (1234) encountered an error (Unexpected TestCaseDidStart...)

Recently we get more and more problems due to non bootstraping or starting simulator clones on parallel testing. Unit & UI-Tests were all successful but the status is failed, because of this errors 'The test runner encountered an error (Failed to prepare device 'Clone 1 of iPhone 12' for impending launch.' The test runner encountered an error (Failed to prepare device 'Clone 4 of iPhone 12' for impending launch. CI environments are MacMinis based on intel and apple silicons, with Xcode 13.3.1.

We got the newly issue that our Test devices keeps us asking for the pin code to "Enable UI Automation". Then it works for some hours or days, but after some time it starts again. "Enable UI Automation" is already enabled in "Settings" - "Developer" menu. The devices are located remotely and we can't access them directly, so this is a big issue for us right now. Is there any way to avoid this?