I was using Twitter's User/Search API with no problem:
https://api.twitter.com/1.1/users/search.json
and
?q=myusername&count=20&page=3
But from yesterday, the paging property seemed not to work.
when I change page value, it returns the same page 1 results.
I even tested my query with https://dev.twitter.com/oauth/tools/signature-generator/ but nothing changed.
I'm sure that I'm not doing anything wrong because it was working yesterday. So what happened?
Thanks for your help.
Edit:
Well it seems something's wrong with twitter REST API:
https://twittercommunity.com/t/rest-api-people-search-json-not-returning-verified-accounts/31381
https://twittercommunity.com/t/users-search-doesnt-show-up-some-verified-account/31388
This issue is solved now. It was a twitter bug (PREL-11824).
More info: https://twittercommunity.com/t/users-search-doesnt-show-up-some-verified-account/31388
Looks like this problem has come back.
https://twittercommunity.com/t/search-problems-have-returned/32573/3
Related
I'm trying to replicate the example of the focal() docs.
When going to the URL:
http://localhost:8888/unsafe/400x100/filters:focal(146x206:279x360)/https%3A%2F%2Fgithub.com%2Fthumbor%2Fthumbor%2Fraw%2Fmaster%2Fexample.jpg
I'm supposed to get this picture as a result:
But I'm getting instead:
Which is the same as if I removed the /filters:focal(146x206:279x360) part, so it looks like it's simply ignored.
What am I doing wrong? I'm using Thumbor 6.4.2.
This seemed to be an issue with this particular Thumbor version.
Upgrading to 6.7.0 fixed the problem.
The '/onenote/sections/{sectionId}/pages' endpoint doesn't return recently created pages. It used to work without issues. Since the past few days, it isn't returning newly created pages. Does anyone know how to fix this issue?
https://graph.microsoft.com/v1.0/me/onenote/sections/{sectionId}/pages?top=100
Thanks for reporting this issue Ajay! It's being investigated and will let you know when fixed.
I have a code written in react-native wherein I'am using a webview to render a website. The URL for same is here
https://cdn.plaid.com/link/v2/stable/link.html?isWebview=true&key=test_key&env=tartan&product=connect&longtail=true&selectAccount=true&clientName=plaid.
When I try to hit this URL, I'am getting Webkit Error domain, Error Code 101. I did research on this before posting the question here. But none of them gave me a workaround.
Below is the code.
<WebView
source={{uri:'https://cdn.plaid.com/link/v2/stable/link.html?isWebview=true&key=test_key&env=tartan&product=connect&longtail=true&selectAccount=true&clientName=Plaid'}}
/>
Please excuse brevity. Any help is appreciated. Thank You.
I was having trouble with this as well, and it looks like the Plaid docs may have a typo in the example URL under "Link WebView Initialization URL". Try using the isWebView parameter instead of isWebview. Seems to work for me.
Switch to isWebview=false. It's working for me. Then catch the messages thrown by the webview in onMessage callback
I don't know why you send those many parameters, for example longtail, i can't find any reference to it.
This is my URL https://cdn.plaid.com/link/v2/stable/link.html?isWebview=false&key=${PLAID_CONFIG.public_key}&clientName=${PLAID_CONFIG.clientName}&env=${PLAID_CONFIG.env}&product=${products}`
Also, as far as I know env should be one of sandbox, production, development.
Old question but worth noting a react-native-plaid
npm package that may address the issue in question.
I'm attempting to add a tableview to an existing UIViewController in my app. The implementation can be found here: https://gist.github.com/naderhen/8161526
It seems to be working okay for the most part, but it doesn't look like the delegate is calling the numberofSectionsinTableView method at all. Throwing some logging text in there returns nothing.
When I run the app in the simulator I get
There don't seem to be any errors in the console...I'm sure I am missing something very simple as I have done this a number of times in the past but can't get it working now.
Any help would be very much appreciated..thank you!
adding
def numberOfSectionsInTableView(tableView)
self.domains.length
end
seemed to fix it
This is an issue I've been experiencing only for the last few days; when following a link to jsfiddle, or even going to the jsfiddle homepage (on IOS 6, iPad 2), jsfiddle doesn't initialise properly, and all I see is "initialising the awesome". Even logging in and creating a fiddle doesn't work. The issue only seems to have appeared since some recent downtime which I assume they were updating jsfiddle during it. Has anyone else experienced this issue/have a fix?
NB: this occurs on both safari and chrome.
Alright, I've sent an email to jsfiddle support, and I came up with this response:
We're working on that.
https://github.com/jsfiddle/jsfiddle-issues/issues/330
For the moment please use draft feature or add /embedded/result to the
URL.
http://doc.jsfiddle.net/basic/introduction.html#draft-page
Regards, Piotr
Hopefully this means that the issue will be fixed soon, however, in the meantime, use: (for example)
http://jsfiddle.net/ (your fiddle)/embedded/result
I.e, just add /embedded/result to the end of the url as Piotr suggested.