I would like to create a recurring payment profile with minute interval instead of day/month interval for testing purposes. I have not found anything in the paypal docs about this.
What part of the application are you testing?
If you're using Payments Standard:
Its probably worth breaking down the testing into various parts.
Payment / PDT can be tested by paying (and then cancelling/refunding the transaction)
I think the IPN can be tested through the simulator, so you can just set that up to test your app.
Related
How much time will it take for Google to finish its review for a extension before it gets published to the Chrome Web Store?
Review times vary; some reviews complete in a few hours, others take many days, and in some cases a review can take several weeks
https://developer.chrome.com/webstore/faq#faq-listing-108
Long time no review, many days, few weeks. Our users can't wait. This is reason why we moved almost feature of extension from Chrome Extension to our own app
So it's weird. The review now take 10 days because they review all versions like its new. So if you make a push and have a small fix it's another 10 days. And sometimes it is more than 10 days.
This means a different strategy towards trying to get your extension deployed. First we are setting up a testing item in the Chrome Store Dev Section so that we can test our extension extensively in Chrome.
Second we are looking at using eval() in order to put our code in a wrapper. We already do this for FF and Safari. The real goal is to move more and more of the processing to the back end so that the need for a deployment becomes rarer.
This sounds like a lot of hoops but if you look at it from Chrome's end and the issues they have had around people doing bad things with extensions this is the price that has to be paid in order to be able to make extensions from their point of view.
I am trying to use mobile web push notifications to enable chat on my site. Since I have a use case to remind users about any updates on the chat - I want to use push notification on the web.
I have experimented with web push notification using FCM and the delivery rate hovers around 60% for me. It is either not delivered (no delivered_time stamp) or gives a 400 error - "Invalid Token format"
I need to understand if there are any improvements I can make to increase the delivery rate? Can it be 100%?
Also, does notifying on mobile web for chat seem to be a valid use case for push notifications or do you think there are better alternatives?
Dump of my log - https://docs.google.com/spreadsheets/d/1oiGkfgiRtoDZTT6bSu9UduHj6IQljj5bFDbliDvbI8I/edit?usp=sharing
Unlike GCM(now FCM) notifications, web notifications need the browser to be open(at least in the background) for them to be delivered. And There are still a lot of anolmalies in the system since it is still marked as an experimental technology. Even though the delivery rate can't be 100%, it becomes more and more stable with every release and the future is bright for web-push-notifications.
We experience a delivery rate of 60-70% on tracking impressions of the campaigns for 36 hours.
I'm building an app which is made of a webserver (currently using NodeJS but doesn't really matter here) and a Chrome extension.
The point of the Chrome extension is to display some data from the server. For this, I need the extension to be aware of changes on the server-side. To do that, I see 3 possible strategies :
1. Websocket
Having a websocket in the background that triggers updates in real time.
2. Regular fetch
But I also can have a timer that will fetch new data on a defined frequency (something like every minute)
3. Event triggered fetch
Another solution would be to detect browser activity, and to trigger a server call during that activity (eg. on active tab changed)
The tradeof I see is browser memory/network usage vs. realtimeness.
To define realtimeness necessity, I'd compare it to an unread email indicator: it doesn't matter if the user is made aware a minute after, but conceptually, it means always displaying out-dated data, which doesn't sound great to me.
On the other hand, if using websockets, or event listeners come at a too high cost and will eventually slow down the browser too much, I'd rather have a minute delay. :)
But maybe fetching the server every minute with most of the time no update to send may be even more expensive than keeping a websocket alive...
Well, any insights on this tradeof and how to choose would be highly appreciated!
Special thanks to #Rob-w for helping me to reformulate the question.
I am testing my in-app purchases, I uploaded my app to the windows store as beta and made an in-app product.
I tried it out and noticed a bug, I want to reset the in app purchase(it is hide ads) but I am not sure how to do this.
I want it so it is like the user account that bought the in-app never actually bought it.
I am going to assume that you are talking about a durable in app purchase, since consumable purchases can be bought as many times as one wants.
Once a durable purchase is made, it is permanent to the account. A user could call customer service to have this reversed, but it is not common (I have done this).
However it is unlikely that a rep would reverse a free in app purchase for a beta app to assist in testing.
If you would like to test your app without having to deal with those issues, Microsoft has provided guidance in how to test in app purchases.
So far as i know, if someone bought something through store, he cannot actually get the money back. If you're releasing app, you should pre-test it to be 100% sure it's working. If you're not sure how is the in-app purchase working, there is a plenty of forum threads about how to do this efficiently. Long story short, if someone already bought this in-app feature, either you cannot block it to him or refund his money.
I'd recommend testing In App Purchases through the emulator. Every time you restart the emulator it's like booting up a fresh device, so you'll be able to purchase IAPs again.
I have a co-worker who has suddenly developed a problem with her Google Calendar. It seems that it has pushed her time slots up one, yet her timezone is correct, and we're in Saskatchewan, where we don't change our clocks!
Ex: Her meeting that she was supposed to have at noon, shows up in the 11am time slot.
The is a recent discovery. Is there a possibility that she did something, and everything shifted? It's not just for one day either, it's for all the events she has. She has it synced with her Blackberry, if that helps at all.
Any ideas, hints, etc are welcome!
I suspect that synchronization with the Blackberry may be to blame. For instance if it was created/synched with a BB device it may have put an incorrect time zone on the calendar event.
One way to check would be to go to Google Calendar and see what time zone is set for the event (It should be GMT - 6 Regina).