Posts

Post not yet marked as solved
7 Replies
786 Views
I have an imessage extension app that works fine except on the first send to a group. iOS 14.4 multiple devices 8, 8plus, 10... Xcode 12.4 The code goes straight from the closure of 'success' to didResignActive. The app is supposed to stay active. There is no dismiss called anywhere. If I launch the app again on the same group it works fine. Only fails if I start a new group conversation, then click on app in tray, and send is called. note: this only happens to group sends, and only on the first time a group is created. thisConversation.send(message) { error in         if let error = error {           os_log("submitMessage(%@): initial send error: %@", log: .default, type: .debug, type, error.localizedDescription)         } else {           os_log("submitMessage(%@): initial send success!", log: .default, type: .debug, type)         }       }
Posted
by ekd.
Last updated
.
Post marked as solved
2 Replies
432 Views
I'm relatively new to ios development, but have quite alot of experience otherwise. So, I apologize if I have the semantics wrong here: I have an imessage application that deals with a conversation/session and has a time limit on when an activity gets communicated to all users in a group (recipients). The application is about 85% done, and this is the last technical hurdle before getting complete. I've tried local notifications, timer callbacks, and performExpiringActivity (in sim and devices). All work great if the user stays in the active state. however, if the user goes to another conversation (say with another user, not in the group) or presses home, none of the above work. I'm assuming this is because the application goes inactive. What I'd like to do is have some kind of notification/badge, alert or whatever to let the user know they need to go back to the imessage app. Or even better launch the app, and execute the callback. Thanks in advance, Roark
Posted
by ekd.
Last updated
.
Post not yet marked as solved
2 Replies
418 Views
When a MSConversation message bubble is recieved (previously sent from the iMessage Extension app), clicking on the bubble has no effect. However, if you click in the Messenger entry (textfield?), then re-click on bubble, the extension app gets called.Is this a bug, or is there something I should have done inside the extension app, to prevent this from occuring? Currently I do the following on a button tap: <...snip...> // Add the message to the conversation. conversation.insert(message) { error in if let error = error { print(error) } } dismiss() <...snip...>Thanks for any guidance.
Posted
by ekd.
Last updated
.