https://web.whatsapp.com/send?phone=&text=
is redirecting to web but not opening the right mobilenumber with text message.
Anything changed ?
Received From WhatsApp Support-We are aware of the issue and we are working on fixing it in a future update of WhatsApp. Unfortunately, we can't comment on any future release dates at this time.
Related
We're using notification_key to group multiple devices. Since yesterday we're unable to send a message to a notification_key. The GCM endpoint returns with status 200 but the response body is empty. The GCM diagnostics inside Google Play shows that no message has been sent to the device and we additionally checked that the message does not arrive at the device.
However, sending a message to a single registration_id (one of which is managed by notification_key) works as expected.
We haven't touched the GCM related code on our side and it was working as expected the days before. I would like to know if this error is known and if other apps are affected as well. Also happy to hear from Google if they were any changes in the last few days.
The issue has been resolved by Google. This is the answer I got from the Google Group thread I've created for this issue:
Hi Andreas,
We had a recent issue in the send API, affecting a subset of the
notification_key requests. That issue should be fixed now.
Please try again. If the API is still not working for you please
report back using:
https://support.google.com/code/contact/gcm_dev_support
Thanks,
- Diego
If they rejected my app and told me to fix the title, is it the ONLY problem/error i have or after a re-upload my app are they going to give me another error for something else?
They just stopped there. If they find your title is correct then they will proceed with the review.
In case the title was the last step in the review (which I doubt) it could be possible that they accepted your app.
Apple's review process is a black box, but I have experience in solving one issue and then being rejected by another issue.
I am currently creating an application that uses local notification. Previously, I coded the message as XXXX, then a few weeks later, I coded the message to be YYYY. And now when I do a test run on my app. Sometimes I get the notification with message XXXX and sometimes I get it with the message YYYY. Anyone has an idea of what is causing the issue?
Found the answer. Apparently, I still have old notifications which shows XXXX
I am working on application in which i am implementing In-App-Purchase,On buying the product through my application i can fetch all the information regarding the products in my console, but the problems occurs where i am not getting the pop-up from App Store which shows all the information to buyers. I cannot figure out the problem. Please suggest some solution for this.
Thanks.
Apple's IAP backend (test mode) has been up and down over the last 5 days, mostly down, there's been no official confirmation of the outage, just check twitter for similar complaints.
need code.. or follow troy brant's awesome tutorial
http://troybrant.net/blog/2010/01/in-app-purchases-a-full-walkthrough/
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