Properly fill array of strings on iOS for DeleteTags

[brismithers]

Description

One Line Summary

Properly fill array of strings on iOS for DeleteTags

Details

Motivation

Fixes #372

Scope

This fix is limited to the DeleteTags method on iOS.

Testing

Manual testing

Using the example app, drive DeleteTags with various length number of tags.

Affected code checklist

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

Checklist

Overview

• I have filled out all REQUIRED sections above
• PR does one thing
  • If it is hard to explain how any codes changes are related to each other then it most likely needs to be more than one PR
• 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.
  • Simplify with less code, followed by splitting up code into well named functions and variables, followed by adding comments to the code.
• I have reviewed this PR myself, ensuring it meets each checklist item
  • WIP (Work In Progress) is ok, but explain what is still in progress and what you would like feedback on. Start the PR title with "WIP" to indicate this.

---

This change is 

[jennantilla]

Interesting! So without count incrementing, the array of keys never finished building, leading to the malformed JSON?

[brismithers]

exactly @jennantilla, might also be a good check to add into the iOS/Android SDK to sanity check the input for null to be more explicit about the failure!