Post

Replies

Boosts

Views

Activity

Reply to Guideline 2.1 response submitted 7 days ago — no reply from App Review or Developer Support
I have one in a similar state. We've now missed a product and service "soft launch" date, and it's messing up investment and early-adopter plans we had. ZERO feedback from apple in weeks and weeks. We're going on almost 5 weeks since initial submission, one rejection that I corrected the issue and resubmitted. I did an escalation already, with again, zero feedback or movement. I've got people pushing me to hurry this along and it's 100% out of my hands at this point. I don't know if it's best to stay on course, or pull the submission and create a whole new one. just don't know.
Oct ’26
Reply to didReceiveRemoteNotification not called in iOS 13.3 when app is in background
Try explicitly setting "content-available" to 1 (integer) (as noted by many others), leave out the alert key, AND the sound entry to an empty string. That made the difference for me, after a rather exhaustive diagnostic session. I was omitting the sound entry and it never worked. I tried setting a sound file name and it never worked. Setting it to an empty string ( "" ) worked fine when accompanied by content-available and omitting the alert key. Printing what I receive (as seen below with my various diagnostic print statements) showed: ["sound": , "content-available": 1, "badge": 0]         guard let aps = userInfo["aps"] as? [String: AnyObject] else {             print( "Incoming failed" )             completionHandler(.failed)             return         }         print( aps )         print( "INCOMING" )
Jan ’22
Reply to Guideline 2.1 response submitted 7 days ago — no reply from App Review or Developer Support
I have one in a similar state. We've now missed a product and service "soft launch" date, and it's messing up investment and early-adopter plans we had. ZERO feedback from apple in weeks and weeks. We're going on almost 5 weeks since initial submission, one rejection that I corrected the issue and resubmitted. I did an escalation already, with again, zero feedback or movement. I've got people pushing me to hurry this along and it's 100% out of my hands at this point. I don't know if it's best to stay on course, or pull the submission and create a whole new one. just don't know.
Replies
Boosts
Views
Activity
Oct ’26
Reply to didReceiveRemoteNotification not called in iOS 13.3 when app is in background
Try explicitly setting "content-available" to 1 (integer) (as noted by many others), leave out the alert key, AND the sound entry to an empty string. That made the difference for me, after a rather exhaustive diagnostic session. I was omitting the sound entry and it never worked. I tried setting a sound file name and it never worked. Setting it to an empty string ( "" ) worked fine when accompanied by content-available and omitting the alert key. Printing what I receive (as seen below with my various diagnostic print statements) showed: ["sound": , "content-available": 1, "badge": 0]         guard let aps = userInfo["aps"] as? [String: AnyObject] else {             print( "Incoming failed" )             completionHandler(.failed)             return         }         print( aps )         print( "INCOMING" )
Replies
Boosts
Views
Activity
Jan ’22