Closed. This question is not reproducible or was caused by typos. It is not currently accepting answers.
This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.
Closed 4 years ago.
Improve this question
lately the FIWARE Lab store doesn't seem to work for me. The first page with Top Rated and Latest offerings loads ok, but after clicking on widgets/mashups tab, it produces an error window:
get() returned more than one Purchase -- it returned 2! Lookup parameters
were {'customer': <django.utils.functional.SimpleLazyObject object at
0x7fd9e41a3750>, 'organization_owned': False, 'offering': <Offering: EntityService>}
Also, when trying to publish a widget, after choosing to upload to the FIWARE Lab Store, the POST request to https://mashup.lab.fiware.org/api/markets/publish fails with code 502 and the following response:
{"description": "Something went wrong (see details for more info)",
"details": {"FIWARE Lab": "Unexpected response from Store"}}
I know that some software components have been updated lately so I understand that this might be a transitional bug. Thanks for your help if you can fix it.
As you pointed, that was a temporal problem. You should be able to use the Store portal again.
Anyway, StackOverflow is for asking questions related to programming (visit the help center for more info), so it's better to use the contact info published on the FIWARE catalogue or the fiware-lab-help#lists.fiware.org for this kind of questions/support.
Related
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 2 years ago.
Improve this question
I am an IT also G suite Administrator.
When I use API explorer : https://developers.google.com/admin-sdk/directory/reference/rest/v1/users/update
I got this error :
Error initializing the APIs Explorer
Cannot find specified method in converted discovery doc.
I check this page : https://developers.google.com/discovery/v1/reference/apis
But I still don't understand.
This seems to be a bug:
Try this API functionality is currently not working for some of the methods of Admin SDK, including the ones from Directory API and Reports API.
Instead of displaying the usual Try this API sidebar:
The message you mentioned is getting displayed:
Because of this, you cannot currently try these methods in the reference docs.
Issue Tracker:
This problem has already been reported before in Issue Tracker, and it has been forwarded internally by Google:
Error initializing the APIs Explorer
Anyone affected by this, please consider clicking the star on the top-left of the referenced issue in order to receive updates and to help prioritizing this.
Closed. This question is not reproducible or was caused by typos. It is not currently accepting answers.
This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.
Closed 4 years ago.
Improve this question
Xcode Quick Help is only showing me "Declared In" information after I downloaded the latest DocSet under the Xcode menu Preferences => Downloads => Documentation.
The Quick Help now has nothing else. It is missing all the other information except for the "Declared In" information.
Now, I have the following docsets in the folder ~/Library/Developer/Shared/Documentation/DocSets
com.apple.ADC_Reference_Library.DeveloperTools.5_1.docset
com.apple.adc.documentation.AppleOSX10.9.CoreReference.docset
com.apple.adc.documentation.AppleiOS7.1.iOSLibrary.docset
I found some information on this from a Google search but nothing that is particularly this problem. It seems like Xcode is getting confused about which docset to use?
Thank you for any help!
Xcode just crashed and after I restarted, the other information on Quick Help is now displayed.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 5 years ago.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.
Improve this question
Sometime in the last two weeks, the documentation for the Google Contacts API has gone offline. It used to be at https://developers.google.com/google-apps/contacts/v3/.
The ContactsAPI does not show up in the newer Google APIs Explorer at https://developers.google.com/apis-explorer/#p/.
Google is usually really good at announcing deprecations and end-of-life dates for APIs and products, but I can't find anything in their blogs about this API, so I can't tell if this is just a mistake or an intentional change.
The Contacts API itself is still accessible via the OAuth 2.0 Playground, so it's not actually offline.
We can access the API documentation in Google's cache of the first URL above, but we're nervous about developing against something whose future is unclear!
Does anyone know what happened to this documentation?
Sbleon, that was really weird for the document offline. But I am using this API in our app and haven't encounter any problem now - so its API is not really offline. Based on my experience on Google API, even new version come out, it will be highly compatible with the older ones. The only problem of Google Api is Domain-wide/Google Apps OAuth 2.0 still not available in some APIs.
Google Contacts v3 Documentation is Down with Error 404 PAGE NOT FOUND for the third day.
We never got an explanation, but the documentation is back up as of today. What a relief!
Closed. This question is not reproducible or was caused by typos. It is not currently accepting answers.
This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.
Closed 1 year ago.
Improve this question
I am attempting to get all tweets fro a specific user with a hashtag. The url I am using is:
https://api.twitter.com/1/statuses/user_timeline.json?q=%23jdmr%2Bfrom%3ABarrySpang
which without the URL encoding is simply: https://api.twitter.com/1/statuses/user_timeline.json?q=#jdmr+from:BarrySpang
When I try it in twitter search (as stated in the API docs) and it displays the desired results, however when I try the above URL I get a 401 response with this error message: {"request":"/1/statuses/user_timeline.json?q=%23jdmr%2Bfrom%3ABarrySpang","error":"Not authorized"}
Please can you advise me on this
statuses/user_timeline doesn't have q parameter
You should be using search: https://api.twitter.com/1/search.json?q=%23jdmr%2Bfrom%3ABarrySpang
I just received the same error when running python-twitter's GetFollowers() method on a user account that had been suspended. If others receive the same error, it might pay to check whether the account you're trying to access still exists.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 5 years ago.
Improve this question
Last year I received two "Technical Support Incidents" in the iPhone developer program, but when I went to renew I found that I would lose them. I have another two for this year, but I'm not really sure about the kind of problems that can be solved by using them.
What kinds of questions are the best use of these Technical Support Incidents? What is the kind of problem I can use them for? What do you receive when you use them? Thanks.
Technical Support Incidents are for when you need code level support for a project you are working on. If your code is hanging up on certain pieces of hardware, or you need help diagnosing a bug in your system, then you can contact the Apple Engineers to help with the particular problem you are having and they will help to resolve the issue.
Notice this is different from a bug in Apple's systems, which is what the bug reporter is for. This is when you need help from Apple to track down a solution to a problem you are having in your code.
I have personally never used it, and with sites like SO, doubt I will unless I hit one of those one in a million edge cases where I code myself into a corner.
More information is on Apple's website.