Fix Nullabity Issue for ATT Timestamp

Author: BrandonStalnaker

ios/RNMParticle/RNMParticle.m

@@ -39,11 +39,16 @@ + (void)load {
     [[MParticle sharedInstance] logScreen:screenName eventInfo:attributes];
 }
 
-RCT_EXPORT_METHOD(setATTStatus:(NSInteger)status withATTStatusTimestampMillis:(NSNumber *)timestamp)
+RCT_EXPORT_METHOD(setATTStatus:(NSInteger)status withATTStatusTimestampMillis:(nonnull NSNumber *)timestamp)
 {
     [[MParticle sharedInstance] setATTStatus:status withATTStatusTimestampMillis:timestamp];
 }
 
+RCT_EXPORT_METHOD(setATTStatus:(NSInteger)status)
+{
+    [[MParticle sharedInstance] setATTStatus:status withATTStatusTimestampMillis:nil];
+}
+
 RCT_EXPORT_METHOD(setOptOut:(BOOL)optOut)
 {
     [[MParticle sharedInstance] setOptOut:optOut];

js/index.js

@@ -101,7 +101,11 @@ const logScreenEvent = (screenName, attributes = null) => {
 }
 
 // Use ATTAuthStatus constants for status
-const setATTStatus = (status, timestamp = null) => {
+const setATTStatus = (status) => {
+  NativeModules.MParticle.setATTStatus(status)
+}
+
+const setATTStatusWithCustomTimestamp = (status, timestamp) => {
   NativeModules.MParticle.setATTStatus(status, timestamp)
 }
 
@@ -651,6 +655,7 @@ const MParticle = {
   logCommerceEvent,
   logScreenEvent,
   setATTStatus,
+  setATTStatusWithCustomTimestamp,
   setOptOut,
   getOptOut,
   addGDPRConsentState,