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
Related
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.
I found a lot of posts about this issue, but none is like mine.
I have a website that subscribes to IG real-time updates. Since some time ago trying to subscribe to new notifications returns the above error. Seems like IG can't reach the callback_url.
Interesting findings while troubleshooting:
I tried to manually (directly) access the callback_url and it works flawlessly.
When I run the site on my local machine and make sure the callback_url is to my server + the verify_token is a valid one then it all works as it should! IG reaches the callback_url.
I used the apigee console to make the subscription request and there it sometimes works.. Meaning - I craft the request to IG API and click Send. If it fails then I click again (I don't change parameters) and then it works..
Web server logs are in line with the results I get (when it complains it can't reach then there's no log of a request).
Does anyone have any tip or suggestion how to fix this?
Thanks!
While chasing my own tail for a solution I also contacted IG support. I described the issue using same description as above.
After 2 weeks suddenly everything started working again. Magic! Suddenly no errors at all! Needless to say nothing has changed on my end (hardware / network / code).
I didn't receive any response from their support, but considering that a previous email to them a few months ago took about 2 weeks to answer then I am quite sure some support guy simply fixed the issue on their side and didn't even bother to let me know what was going on.
This could be related to the fact that they killed most of their real time notifications API.
Anyway, leaving this here so that if anyone encounters a similar issue then just know you may need to email IG support.
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
I've updated my iPhone app to support the iPhone 5 screen..
I've done this before for another app and I was forced to upload new screenshots taken with the iPhone 5.
This time however, iTunes Connect just displays the status as "waiting for review" and isn't mentioning anything about the screenshots..
I'm slightly worried something has gone wrong? App works great on iPhone 5 and simulator though.
It turns out Apple can block apps during the review process that have something wrong with metadata. If they decide your metadata is wrong they'll just change your app's status to "Metadata Rejected".
Here's the quote from the rules for this status:
Appears when specific metadata items aside from your binary have not
passed review. To resolve the issue, edit the metadata in iTunes
Connect and your existing binary is then reused for the review
process. You receive a communication from App Review in the Resolution
Center regarding the reason for the metadata rejection.
When things change to the AppStore (Apple adds a device) they might require you to get new screenshots. But if nothing changed in their system, it's normal that they don't ask.
Don't worry!
They copy over the screenshots from your last version of the app (or is your Retina4 screenshot section in itunesconnect empty?). So if you don´t want to update them, it should be okay like this.
Chances are your app has not hit review (and now as of the 21st) and won't be reviewed until after the 29th. Once your app hits review, it will become rejected for the missing screenshots. If you want to save yourself some time and pain, update the screenshots while Apple is on their downtime for the Christmas holiday. You'll thank yourself later.
My app got accepted yesterday, no word about the screenshots.
App works fine on iPhone 5, mailed Apple to complain this probably is a bug (iTUnes Connect does not recognize localized Default.png, which is what is checked to verify it is iPhone 5 optimized I believe.)
I am writing an mac application for the Mac App Store that uses in app purchase. I double checked and I think I have implemented everything correctly. So when I am making a product request the delegate method
- (void)productsRequest:(SKProductsRequest *)request didReceiveResponse:(SKProductsResponse *)response
is called, with the correct product id. Then I make a payment using
[[SKPaymentQueue defaultQueue] addPayment:payment];
The issue appears at this point. In the first 10-15 minutes the purchase dialog does not show up at all, and I neither do I receive the updatedTransactions notification. After some time if I try again, everything works correctly, I am prompted in 1-2 seconds for my credentials. This seems very strange for me, because they should work from the start.
Because of this my app was rejected several times, stating that in app purchases do not work.
Yes, I have added the receipt verification code, and if it doesn't exist then I exit the app with code 173, I am prompted for my credentials, then the app reopens but the in apps do not work even after this. And yes, I have tested this with a built that has been created with a distribution profile. I am using XCode 4.2, and my OS is Lion.
After adding the payment to the queue, I tried starting a timer to check the transactions property of SKPaymentQueue periodically. The transactionIdentifier is the correct one, and it's transactionState is SKPaymentTransactionStatePurchasing. This tells me that there is some communication issue between StoreKit and the Apple servers.
Anyone else experienced this issue? Any help would be appreciated, I am struggling with this for 3 days now and could not find a solution for this, and it's driving me crazy.
I've found the answer at last. I have indeed implemented everything correctly according to the In App Purchase Programming Guide.
It seems what I've been doing wrong is to add the transaction observer, before the receipt verification code. After I have changed the order (first verify the receipt, then add the observer) everything worked correctly. This detail should be mentioned somewhere. It caused a lot of headache.