Basically I want to get an event that the message has been received and send that message to my database (database bit already works)
I've tried all npm solutions including react-native-android-sms-listener, react-native-get-sms-android and other, but none seem to work, I've read somewhere, that expo may not support sms reading, but don't know how to use anything else for this sort of task
Nope, It is not available for now in expo variant, regarding Bare Workflow, there are few solutions that helps in reading the SMS
Related
In all the react-native tutorials I have seen so far, on building a chat app, I see them using gifted chat.
After installing the library, it is really buggy and slow. Below are some things I experience when using it.
When I have messages over 100, it takes time to load my chats.
When I press the send button, It takes time as well before updating the chat list(about a second).
Are there any other alternatives to gifted chat?
Slowness or fastness would depend on the "backend" (database and/or server) you are integrating your chat app (or component) with. Firebase (from Google) FireStore or Firebase Realtime DB would be one of the best options to choose from. This might help you in integrating Firebase DB with gifted-chat.
react-native-gifted-chat seem not to be actively maintained.
I found react-chat-elements I did not try it yet.
If you found something else please leave a comment.
good look with your search.
I've recently encountered this post where the general idea is how to subscribe a user to a topic, with multiple devices. I provided an answer, suggesting to make use of the Device Group, then doing the batchAdd on the server side.
But I was wondering if it was possible to subscribe to a topic using the device group notification_key?
I haven't seen anything that mentions something like that in the docs.
The notification key is described in the doc as:
All devices in a group share a common notification key, which is the token that FCM uses to fan out messages to all devices in the group.
So I thought maybe it was possible to use it. But can't find anything that mentions it though. I've looked around the community for any other similar posts, went through the docs, but most of it are just about subscribing a single device to a topic.
Was my answer to the post a good method? Or did I just miss something where there is already a process/flow on how to actually do this?
I haven't really tried it out myself, but it was the only way I could think of. I'm still studying about GCM & FCM and I would appreciate it a lot if someone that tried it before can shed some light about this.
You cannot subscribe a device_group to a topic. The way to achieve this would be to subscribe the tokens associated with the device group to the topic either individually or in batch.
Question says it all. All the examples I can find are for server<-->android.
I'm looking for Javascript-->android
Paid version, try PubNub (Push to Android Example) or Pusher API tools.
For open source solution, you might try PushSharp
Note the real trick is obtaining the RegID from your device. See the answers in this posting to understand better what is going on...
According to this blog post the new messaging system should be accessible via the API (fql/graph) for non developer account as of end of November. It still gives OAuthException with message "You must be a developer of the application".
I was unable to find any updates on this issue from Facebook or other sources. Anyone knows what is going on with this and when will it be accessible?
There was a bug opened on the subject, anyone who has interest in this might consider promoting it.
Going to answer my own question, according to the response on the bug seems like the official answer is:
"We said it would be published but it wasn't, so just wait until we say it will be published again".
Are you trying to read messages or send them? It's still not possible to send them but reading them should work for any app now
I'm trying to send multiple notifications using my PHP script. But after sending about 50 or so out of the 10k users, I get a broken pipe warning. I'm not sure whether that message is sent.
From various other posts, I learnt that it could be because of a invalid token. However, my feedback service returns no invalid tokens. (ssl://feedback.push.apple.com:2196) Tried this both in production mode and sandbox mode.
What other reasons could cause this invalid pipe issue?
My exact problem is explained here by someone else as well.
http://pastie.org/698787.txt
Apple's servers will drop the connection as soon as there is something wrong in the stream of your push messages.
Be careful with mixing device tokens between sandbox and production modes. There's an article here that describes the issue.
Also, have you tried using the enhanced notification format described in Apple's documentation? The response might tell you what's wrong.