Is there a way I can retrieve received messages and save them in a host app using an iMessage extension ?
Absolutely no way. This is a question of privacy, Apple will never let any extension read/save messages from users.
https://developer.apple.com/videos/play/wwdc2016/224/ :
Apple is very, very concerned about user privacy and we really very highly value the privacy of our customers, so we don't expose contact information at all to iMessage apps.
The only thing you can do, is retrieving messages sent via your iMessage extension, within certain conditions (if the user has selected the message for instance)
Related
I'm planning to write a slack app, and I need to render messages depending on who read them.
I'm thinking something like: the App should have some options, and user's clients should render the messages depending on the options chosen by the user.
Is there a way to post a persistent message (I mean not an ephemeral message) which is shown only to a user (or a set of users)?
Or
Is it possible to post a message shown differently depending on the user who read it?
I don't need to send private or sensitive data, so if the solution to my problem is a message containing all the content for all the users in the channel, it is perfectly fine. It's just matter of user experience.
I have two constraints:
The user experience for those who don't use the App should not be impacted
I need the messages from the App to be rendered in reply to messages sent by the users, so solutions like "open a new channel" or "send direct messages" are not suitable for my needs.
Thank you all (but the Slack team which, in case let us doing that, it makes that not clear in the documentation :D )
This is not possible unless you create your own client to show/display the messages.
Custom slack apps usually augment to the existing functionality. How do you expect to override the functionality of Native Slack 'Desktop, Mobile & Web' Client.
I am happy to discuss this further, if you have some approach in mind.
When my bot is first installed on a Teams tenant, I appear to have no way of localizing that message. Most of my Teams app is currently localized by the browser locale available with all messages sent to it by users.
However, when a bot is added to a team (membersAdded), this locale information is not present.
Since I use graph for other app needs, I try to leverage the users preferred language, but that cannot be done without first granting the app permissions to use graph. This means that the first time the bot is added to a team, it is never localized. After app permissions are granted by the user, future welcome messages in other teams are localized, but that also has the limitation that the locale used by the welcome message doesn't necessarily match the users current browser language preferences.
Is there another way to localize the welcome message the bot sends out?
This is a known limitation currently. Bot has to wait for user to message. The message activity has clientInfo filled out in channelData with locale information.
When a new user signs up, we're going to give them a checkbox where they can Opt-IN or Opt-OUT of receiving SMS messages.
I can easily track this on my own by making sure our application doesn't send texts their way, but I'm wondering if it makes more sense for me to just add them as opted out on Twilio?
I'm still playing around with this idea, but regardless I'm not seeing any API endpoints (https://www.twilio.com/docs/api) for Opt-In or Opt-Out.
Questions:
How would I Opt-Out a phone number if I choose to go that route?
Is it better to manage this list on my end, or to use Twilio for this (if it's possible), or to be redundant and manage my own list in addition to Twilio enforcing it?
Twilio developer evangelist here.
There is no API for developers to opt users' phone numbers in or out of messages so you should maintain that opt out list yourself within your own application as you described at the start of your question.
Twilio does make it possible for users to completely opt out of messages from a number (or messaging service) using the industry standard opt out words (STOP, STOPALL, UNSUBSCRIBE, CANCEL, END, and QUIT). When a user sends one of those words on their own to your number then Twilio will cease sending messages to that person. You will receive the message as a webhook so you can watch for those keywords and update your application's opt out list too.
I recommend that if you want users to opt out of messages that you get them to do so as part of your system rather via the STOP mechanic. That way, to re-enable messages they can do so through your system and not have to send an opt in message (START, YES and UNSTOP) to open up to messages again.
I am trying to figure out how to use sinch to build a basic group messaging app. It looks pretty simple but I have a few questions to help me understand the platform:
1) It seems like the platform doesn't support multiple conversations for one user. For example facebook messenger allows you to have many conversations with different people (different chats). But sinch only lets you send a message to a user with no conversation meta data. Or is it possible to send your message with meta data?
2)Do you manage users on the sinch platform? This means creating user objects and giving them id's etc or must this be done on another platform like parse?
3)How do you handle messaging logs? Like if I send a message to someone that's not logged in- how do I save it and also send them a push notification that a message was sent?
Thanks for the help everyone- the documentation is a bit dilute so I haven't been able to find answers to these questions yet :/.
You can send meta data with headers, to create your own meta data thing. But to be fair Sinch is more like multi recipient message than groups with channels.
No, we use delegated security
We will automatically deliver the message when the user logs on, we keep messages for 30 days for delivery.
With the new iOS5 is there a way that you can read incoming iMessages and write new iMessages using a custom app?
I don't think that would be possible. Allowing third party apps to read users' messages would be a severe privacy violation.
Your app can't read them, but it can allow the user to write and send one using MFMessageComposeViewController.
Note that it will use SMS when the receiver isn't using iMessage.