I'm trying to lookup my app from this method: http://itunes.apple.com/US/lookup?bundleId=com.writingfuture.where2
But it always return
{
"resultCount":0,
"results": []
}
My app status in the store is perfectly fine (ready for sale). Here's a detail:
Bundle ID: com.writingfuture.where2
Apple ID: 467311933
Type: iOS App
Version: 2.0.1
Status: Ready for Sale
Date Created: Dec 4, 2012
Date Released: Dec 10, 2012
I have no idea why I can't lookup for my app with this method.
Do you guys have any idea?
Thanks in advance,
Chammp
Looks like your app is ONLY available in Thailand storefront - so the lookup should include country code in the base lookup URL:
http://itunes.apple.com/th/lookup?bundleId=com.writingfuture.where2
The alternative to using bundleId is simply looking up by adamID:
http://itunes.apple.com/th/lookup?id=467311933
If your app is available only in Thailand you should add info about country in request
http://itunes.apple.com/lookup?bundleId=com.writingfuture.where2&country=th
Related
I send request via REST API
https://www.mysite.pl/rest/V1/orders/89
And have date and time:
"created_at": "2021-09-21 15:59:34",
When I go to Saels->Orders in admin there is different data and time:
"Sep 21, 2021, 5:59:34 PM"
So there is a 2 hours difference. I think this cause a problem with my payment module. In admin timezone is set to CET Warsaw. Why in REST API call there is other time ?
I fixed this issue for me by selecting the "Coordinated Universal time" in admin:
Store -> configuration -> General -> General -> Local Options
I am having trouble with the migration of the Ruby SDK from Amadeus Flight Low-fare Search to Flight Offers Search
I'm currently using the Ruby SDK for my student project , and just got the notification about the migration of Amadeus Flight Low-fare Search to Flight Offers Search.
It looks like the SDK endpoint amadeus.shopping.flight_offers.get() is still going to Low-fare Search instead of Flight Offers.
I tried updating my parameters for the transition to Flight Offers Search as so:
response = amadeus.shopping.flight_offers.get(
originLocationCode: origin,
destinationLocationCode: destination,
departureDate: departure_date,
returnDate: return_date,
adults: 1
)
And received the following error:
Amadeus::ClientError ([400]
[origin] This field must be filled.
[destination] This field must be filled.):
And while the following request works, this is reaching the Low-fare Search instead of the Flight Offers Search:
response = amadeus.shopping.flight_offers.get(
origin: origin,
destination: destination,
departureDate: departure_date,
returnDate: return_date
)
I've noticed that the documentation shows that amadeus.shopping.flight_offers.get is the namespaced client for /v1/shopping/flight-offers, while it looks like the Flight Offers endpoint is /v2/shopping/flight-offers.
Is there a different Ruby SDK endpoint I should be using to access the Flight Offers Search?
The Ruby SDK was not fully updated. I just released a new version 5.0.0 adding the support for Flight Offers Search and Flight Choice Prediction v2 and removed the support of Flight Low-fare Search and Flight Choice Prediction v1.
You need first to update your amadeus library:
gem install amadeus
You can then use the Flight Offers Search API:
amadeus.shopping.flight_offers_search.get(originLocationCode: 'NYC', destinationLocationCode: 'MAD', departureDate: '2020-10-01', adults: 1)
I have a reservation application with a c# mvc api mssqlserver backend and angular frontend, everything is fine in Chrome on browser
however when I go to Safari IOS the dates are off by a single day
for example - on browser: 28th reservation( fromdate:28th todate: 28th)
startdate: 2018-06-28 00:00:00.0000000
end date: 2018-06-28 00:00:00.0000000
- on IOS safari: 28th reservation(fromdate: 27th todate: 27th)
example: 2
on browser: june28th-july19th
on IOS safari: june 27th - july 18th
the dates are retrieved from the db table and I can ensure that their format is
(2018-06-28 00:00:00.0000000)
Additionally, I noticed that when I get that exact datetime on ios it's different than browser- for example, I checked into my reservation at 11:08am and on IOS it showed the same date/time as 7:08am this could possibly be a factor but I don't know how to approach this issue
The following query using the Yahoo API started to return a result of 'null' since yesterday. (in fact all my queries against the geo.placefinder) return result: null.
Is anyone aware of an update / work that yahoo is doing? I have tried using their developer console but that returns null result as well. This query is a crucial part of my application that now is dysfunctional.
https://query.yahooapis.com/v1/public/yql?q=select%20*%20from%20geo.placefinder%20where%20text%3D%22sfo%22&format=json
I have encountered the same problem, as I understand the placefinder was meant to be shutdown on Nov 17, 2012 and we were meant to use the paid service Boss Geo.
see:
https://developer.yahoo.com/blogs/ydn/introducing-boss-geo-next-chapter-boss-53654.html#more-id2
YQL tables for development
If you are looking to continue experimenting with the standalone PlaceFinder and PlaceMaker services, we are excited to continue supporting you through our YQL tables. These tables will be limited to 2,000 queries per day and are meant for non-commercial usage. We intend to shut down the current free versions of PlaceFinder and PlaceMaker on November 17, 2012.
Workaround:
For a direct replace of the current url you can use a combination or YQL and gws2.maps.yahoo.com. For example, to get the location of the random co-ordinates below the url will be the following:
var url = https://query.yahooapis.com/v1/public/yql?q=select%20*%20from%20xml%20where%20url%20%3D%20%27http%3A%2F%2Fgws2.maps.yahoo.com%2Ffindlocation%3Fpf%3D1%26locale%3Den_US%26offset%3D15%26flags%3D%26gflags%3DR%26q%3D52.01%2C4.82%27&format=json&env=store%3A%2F%2Fdatatables.org%2Falltableswithkeys
to execute it with ajax it would be something like the following:
$.ajax(
{
url: url,
type: "GET",
headers: { "Accept": "application/json; odata=verbose" },
success: getWeatherForLocation,
error: appErrorHandler
});
This is the same as the post at Yahoo YQL query with gFlags returns nothing
Several solutions to this are posted on that thread.
Im making an ipn handler for my iOS Application.
Im using classic paypal api with my app.
The thing is when i test from the PayPal IPN Simulator it works fine.
I got the post message below from the simulator (with express checkout i dont remember):
map[
business:[seller#paypalsandbox.com]
item_number1:[AK-1234]
receiver_id:[seller#paypalsandbox.com]
first_name:[John]
mc_shipping1:[1.02]
tax:[2.02]
residence_country:[US]
txn_type:[cart]
mc_shipping:[3.02]
test_ipn:[1]
custom:[xyz123]
mc_handling:[2.06]
mc_handling1:[1.67]
payer_id:[TESTBUYERID01]
payment_status:[Completed]
receiver_email:[seller#paypalsandbox.com]
mc_currency:[USD]
verify_sign:[AdsvkafFyuBADI8IS081RggbvUxmAu2ntBemAGacZ3Dx56qQzmc9QzhK]
address_country:[United States]
item_name1:[something]
mc_fee:[0.44]
address_state:[CA]
mc_gross1:[9.34]
payer_status:[unverified]
last_name:[Smith]
invoice:[abc1234]
payment_date:[07:44:54 23 May 2013 PDT]
address_city:[San Jose]
mc_gross:[12.34]
address_street:[123, any street]
notify_version:[2.4]
txn_id:[298300930]
payer_email:[buyer#paypalsandbox.com]
address_status:[confirmed]
payment_type:[instant]
address_zip:[95131]
address_country_code:[US]
address_name:[John Smith]
]
But when i tried to test with a Sandbox account i got the post message below which also works fine:
map[
fees_payer:[EACHRECEIVER]
transaction[0].id:[89799058XE923193M]
verify_sign:[AE6aVMFpE6M3pfCoNe9gPQ4pMixOA9NNUFbTWPTrOik1CqrdIVxc3K3M]
pay_key:[AP-9DJ400382D973781B]
transaction[0].id_for_sender_txn:[8MC20151R46812309]
transaction[0].status:[Completed]
action_type:[PAY]
transaction[0].is_primary_receiver:[false]
sender.useCredentials:[true]
transaction[0].pending_reason:[NONE]
transaction[0].amount:[USD 29.00]
payment_request_date:[Thu May 23 07:46:49 PDT 2013]
reverse_all_parallel_payments_on_error:[false]
test_ipn:[1]
status:[COMPLETED]
transaction[0].status_for_sender_txn:[Completed]
transaction[0].paymentType:[SERVICE]
notify_version:[UNVERSIONED]
transaction[0].receiver:[mail-facilitator#something.com]
return_url:[http://www.paypal.com]
log_default_shipping_address_in_transaction:[false]
charset:[windows-1252]
cancel_url:[http://www.paypal.com]
transaction_type:[Adaptive Payment PAY]
ipn_notification_url:[http://something.com/ipnhandler/]
]
But as you can see there is no similarity between these two and there isn't anything usefull for me here.
With simulator i got payer name , email etc. but with using a Sandbox account i think i only notify myself that i got a payment.
I wonder why is this happening and is it gonna be like this when the app live.
A little late, but yes, the IPNs that are being sent as a result of adaptive payments are different because the transaction is different. For example, since there can be multiple receivers, having a single receiver_id field wouldn't make sense. Paypal provides an overview of all fields and possible values: https://developer.paypal.com/docs/classic/adaptive-payments/integration-guide/APIPN/