fbq("track","Purchase",{value:140.96,currency:'TL'});
Facebook is giving pixel error. But I do not see any problems. Do you see any problems?
fbq("track","Purchase",{value:140.96,currency:'TRY'});
All supported currency should be 3 chars. I hope when you specify TL, you mean Turkish Lira (i.e. TRY)
Related
Note: I've answered my own question here, and am posting so that others in the same situation may benefit.
I was following along with various WebGPU tutorials, in particular for compute shaders, these articles in particular: https://web.dev/gpu-compute/ and https://surma.dev/things/webgpu/ -- and obviously the WebGPU specifications have been adjusted since these articles were last updated.
The first error I encountered, was in WGSL, that #stage(compute) had been deprecated in favor of #compute -- this was an easy fix :)
However, the next error, had me stumped:
Tint WGSL reader failure: :9:46 error: access mode 'write' is not valid for the 'storage' address space
#group(0) #binding(2) var<storage, write> resultMatrix : Matrix;
^^^^^^^^^^^^
- While validating [ShaderModuleDescriptor]
- While calling [Device].CreateShaderModule([ShaderModuleDescriptor]).
Another message was also output:
1 error(s) generated while compiling the shader:
:9:46 error: access mode 'write' is not valid for the 'storage' address space
#group(0) #binding(2) var<storage, write> resultMatrix : Matrix;
The fix is simply replacing the following WGSL line:
#group(0) #binding(2) var<storage, write> resultMatrix : Matrix;
With the following fix:
#group(0) #binding(2) var<storage, read_write> resultMatrix : Matrix;
I managed to figure this out based on a table in this section of the WGSL specification
I'm trying to get quotes for an Australian stock with ticker A200.AX (aka A200.AUS) from Alpha Vantage.
I have no issues getting other symbols from the AX market, e.g.:
https://www.alphavantage.co/query?function=TIME_SERIES_DAILY&symbol=ETHI.AUS&apikey=demo
...returns data as expected
However when a symbol has digit(s) in it, it seems to return an error:
https://www.alphavantage.co/query?function=TIME_SERIES_DAILY&symbol=A200.AUS&apikey=demo
Invalid API call. Please retry or visit the documentation (https://www.alphavantage.co/documentation/) for TIME_SERIES_INTRADAY.
Same result for F100.AUS
I checked to make sure the ticker was valid: A200.AUS shows up if I search for it:
https://www.alphavantage.co/query?function=SYMBOL_SEARCH&keywords=A200.AUS&apikey=demo
I'm aware of some questions related to URL encoding, but I can't see any URL special characters in A200.AUS . Besides, using the search endpoint works with the ticker passed on literally.
Does anyone know how to download this stock's information or what I'm doing wrong?
Your use of the search endpoint is great, however A200.AUS is an ETF. Alpha Vantage has some ETFs, but currently, only 100% supports stocks.
Right now the Facebook API is returning a URL like this with all post/album images 130x130 pixels in size:
https://fbcdn-sphotos-h-a.akamaihd.net/hphotos-ak-xfp1/v/t1.0-9/s130x130/10801504_570625556403546_6496651209845129904_n.jpg?oh=dcf8ab3752522532871d2aaab09b6e7e&oe=54E4402F&gda=1424027679_76464aeeaa5d232b8100d01476af4ec7
How do I retrieve a full (or any bigger size) image based on that URL?
For example this one:
https://fbcdn-sphotos-h-a.akamaihd.net/hphotos-ak-xfp1/v/t1.0-9/p417x417/10801504_570625556403546_6496651209845129904_n.jpg?oh=cd2b5cb0d74f7306c098de9f56dc6e27&oe=54E1F4C1&gda=1423830001_e700bfac39039952bfee55b200c158bf
or anything like that?
All the other suggestions of removing s130x130 from the URL, or /v/t1.0-9/, or replacing _s with _n or anything like that aren't valid any more - I've tried them all (try them yourself if you don't believe me). Is there a way to make this happen? Not sure what Facebook guys have changed to disable that...
After a couple of hours searching and pulling my hair out, I found a solution that works for me. In my case I'm pulling posts from {page-id}/posts, but I'm pretty sure this will work for you too, seeing that I used to get larger images using the same approach as you mention.
This is works for me:
bigger_image="https://graph.facebook.com/" + picture_url_from_facebook.match(/_\d+/)[0].slice(1) + "/picture?type=normal";
/_\d+/ matches any substring starting with an underscore (_) followed by any digits (\d matches one digit, \d+ does the digit match over and over until it fails)
match(regex) returns an array with all strings it could find matching the specified regex
we grab the first ([0]) element, as this will be an underscore followed by the ID of the picture in Facebook's database
we slice the string from index 1 to the end, as the underscore is not a part of the ID
we then get a working link from facebook using the graph api without the need for any extra calls (you can use this in for example an img tag directly)
You can see this working in action # this fiddle or this page we did for a client
Thanks to Er Adhish for leading the way to the solution # https://stackoverflow.com/a/27075503/2908761
https://graph.facebook.com/{object_id}/picture?type={thumbnail|album|normal}
Example (using a bogus object_id of 122233334444555):
https://graph.facebook.com/122233334444555/picture?picture?type=large
Make sure object_id is not just the id of an item but it's object_id (which is typically the number following the underscore in the full id).
I got those type values from a helpful facebook response message that said:
"message": "(#100) type must be one of the following values: thumbnail, album, normal"
In place of ?type=... you could do height/width as well:
?width=543&height=543
I'm running into the issues since today. The way I was keeping the user name unique was creating it as ${FACEBOOK_FIRST_NAME}_${FACEBOOK_ID} and WarpClient.GetInstance().Connect(${FACEBOOK_FIRST_NAME}_${FACEBOOK_ID}) worked just fine till now.
Today it stopped working, and after trial and error it seems that the username length is limited to 21 characters now. 22 characters user name causes CONNECTION_ERROR, 23 and more - BAD_REQUEST.
Is it a new restriction introduced, and if it is, what is the best way to maintain unique but readable user names based on users FB credentials?
10x
There are restrictions on the username string.
The length should be less than 25 and the following characters are not allowed
, ; \ /
See the API reference.
http://appwarp.shephertz.com/game-development-center/csharp-api-reference/#connect
Hope it helps.
I've been using the iTunes API in my app for a while now, but as of the last few days I've noticed that it is returning odd results. I currently use it to search for software however it's now started adding Software Artists to the results which I believe to be incorrect with the search parameters. Below is a URL searching for my app, and below that is the returned JSON.
http://itunes.apple.com/search?term=AppTracker%20Deluxe&limit=100&entity=software&lang=en_GB&country=GB
{
"resultCount":2,
"results": [
{"kind":"software", "features":[],
"supportedDevices":["iPhone5s", "iPadMini", "iPhone5c", "iPadFourthGen", "iPad2Wifi","iPad23G", "iPadThirdGen", "iPhone5", "iPodTouchFifthGen", "iPadThirdGen4G", "iPhone4", "iPadFourthGen4G", "iPadMini4G", "iPhone4S"], "isGameCenterEnabled":false, "
cutting most stuff out for space
"languageCodesISO2A":["EN", "FR", "DE", "IT", "ZH", "ES"], "fileSizeBytes":"3575818", "trackContentRating":"4+", "averageUserRating":5.0, "userRatingCount":5},
{"wrapperType":"artist", "artistType":"Software Artist", "artistName":"Handyman Interactive", "artistLinkUrl":"https://itunes.apple.com/gb/artist/handyman-interactive/id586907831?uo=4", "artistId":586907831}]
}
As you can see, on top of returning the correct app, it is returning a software artist (myself in this case) which it hasn't done in the past. Obviously I can update the app to ignore these, but for the current version of my app it is causing slight bugs. Is this a problem down apples end or is it intended?
Thanks for the help,
Mike
Turns out it was a bug and the behaviour is no longer present.
Mike