Using reflection for iOS 13 API writeData:error:

[emawby]

Description

One Line Summary

Using reflection for the iOS 13+ writeData:error: api introduced in pr #1029.

Details

Our build scripts still require Xcode 10 which is not aware of iOS 13+ APIs. PR #1029 added an iOS 13 API, but did not use reflection for it resulting in build failure when trying to release a new binary.
We need to use NSInvocation for reflection because performSelector cannot take pointer parameters.

Motivation

This PR fixes using an iOS 13 api without reflection which caused build failure for the build_fat_framework.sh script.
This issue was introduced by pr #1029

Testing

Manual testing

I tested both success and failure on an iOS 15 device. The error had a proper description and when successful the image appeared in the notification.

Affected code checklist

• Notifications
  • Display
  • Open
  • Push Processing
  • Confirm Deliveries
• Outcomes
• Sessions
• In-App Messaging
• REST API requests
• Public API changes
• Distribution

Checklist

Overview

• I have filled out all REQUIRED sections above
• PR does one thing
• Any Public API changes are explained in the PR details and conform to existing APIs

Testing

• I have included test coverage for these changes, or explained why they are not needed
• All automated tests pass, or I explained why that is not possible
• I have personally tested this on my device, or explained why that is not possible

Final pass

• Code is as readable as possible.
• I have reviewed this PR myself, ensuring it meets each checklist item

---

This change is 

[jkasten2]

Reviewed 1 of 1 files at r1, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @emawby)