Just an update...
I was told to file a bug report for this (which I did).
I also supplied a video which shows how to reproduce the bug.
This is the message sent back from support...
Hi,
Thank you contacting Apple Developer Technical Support (DTS).
There is no workaround DTS can provide for Feedback ID #FBxxxxxx; it
is still under investigation. Please continue to track the problem via
the bug report.
...
Post
Replies
Boosts
Views
Activity
I modified the above code and tried this... same result...
DispatchQueue.main.asyncAfter(deadline: DispatchTime.now() + 2.0, execute: {
conversation.send(message) { error in
if let error = error {
os_log("submitMessage(): initial send error: %@", log: .default, type: .debug, error.localizedDescription)
} else {
os_log("submitMessage(): initial send success!", log: .default, type: .debug)
}
}
})
When you open iMessages, click on the compose icon top right. Add two recipients. Then click on the application icon (in this case my app), below the text entry field in the application list tray( same place as the appstore icon and other apps like gif, apple pay, etc.
I was able to create a test app that reproduces this problem, with what I think is the minimal amount of code to demonstrate. Hope this invites a solution! }
I don't create the group in code. the group is the list of recipients passed in to the app by imessage in the conversation object. The fact that a fresh launch of the application with only a single recipient works fine and a list of recipients fails is telling. Also, a fresh launch of the app in an existing group conversation works fine.
What code would help? I have hundreds of lines of code here. Clean build, no crash in debugger, just jumps to DidResignActive.
I've noticed that if I create a group, then send from the imessage entry a single text (can be just a character), then click on my app in tray it works fine. It's only if you click on the app in the tray w/ out first sending anything else on a group.
bump... interested as well
Just got off a lab 1-1 session w/ an apple guy. prsr nailed it. Or so I hope. I was shown how to add an iOS container (single view) to my existing iMessage extension app. We discussed ways for the iOS part of the app to handle notifications, etc. when the extension goes inactive. Here's my reading assignments that pertain to this:
https://developer.apple.com/documentation/usernotifications/setting_up_a_remote_notification_server/pushing_background_updates_to_your_app
https://developer.apple.com/library/archive/documentation/General/Conceptual/ExtensibilityPG/ExtensionScenarios.html
Hope this helps...
Also happens in simulator...
Forgot to add this is between iPhones, not simulator.