I downloaded the Vidyo SDK for iOS. I followed the all the steps to generate a new token and succeeded on that. But at the time of joining the call it always prompting Unexpected disconnection. Even in the VidyoConnector Mac app also getting same error. Led to conference inability.
What are all the possibilities of hitting this error. Any help much appreciated!
Based on your description, it seems like the token you have generated is invalid. How did you generate it ? Here is a link that provides with token generation scripts samples in multiple languages.
https://support.vidyo.io/hc/en-us/articles/115003127747-Generate-a-Token
Another tip to validate your token - it's a long string that ends with "==" symbol.
Are you using the python script shared at https://static.vidyo.io/4.1.16.8/utils/generateToken.py
The syntax for using our pyton token generation:- python3 generateToken.py --key= --appID= --userName= --expiresInSecs=10000
Make sure that you do not include any special character like # in the user name
Related
Very recently I got an academic access to Twitter API and I would like to start getting some data. Unfortunately, when I run the code I keep getting: "SyntaxError: invalid decimal literal'. It looks that something it is wrong with my bearer token.
In this video https://www.youtube.com/watch?v=rQEsIs9LERM&t=7s, I found the following code:
also here: at n.3 https://github.com/jdfoote/Intro-to-Programming-and-Data-Science/blob/fall2021/extra_topics/twitter_v2_example.ipynb
Unfortunately, every time I try to run the code I got an error that points to the number after the % in my bearer token. One example here:
I tried to regenerate the bearer token multiple times by with no avail. Also, the definition of invalid decimal literal that I found on the internet doesn't seem to help. Any thoughts? Thanks in advance for your time!
Ps. sorry for including the image but the website kept rejecting the indentation of the code.
the solution was banal: it works just adding the quotation marks to the bear token.
Going from version 2.9.3 -> 2.18.0 for the ruby gem.
Have been using v4 for Recurly.js so that stays the same.
This has been working for years and I decided to upgrade the gem.
I am generating the front end token with:
recurly.configure({ publicKey: RECURLY_JS_PUBLIC_KEY })
It generates a token and pass it along to the backend where we do:
Recurly::Account.create!(
account_code: account_code,
billing_info: { token_id: params['recurly-token'] }
)
It keeps raising this error:
Recurly::Resource::Invalid (billing_info is invalid)
I've been messing around with this a lot. Putting in a random string as the token or waiting 20 minutes for the token to expire will throw a different error message:
Recurly::Resource::Invalid: Token (billing_info.token_id) is either invalid or expired
So I feel like it is reading my token correctly and the keys are correct. Could it be that maybe the billing info that I used to generate the token be bad? I've filled out so many different combinations of correct addresses and test credit card numbers.
I'm out of ideas and any help would be nice.
It does sound like the actual billing information might be bad. Are you using the correct test card number (4111-1111-1111-1111) with an expiration date in the future, and all the address information required by your site settings?
Figured out the issue.
There was a problem with the country input. Originally the ISO alpha-2 code worked for the country. But once I updated the gem, the ISO alpha-2 code no longer worked. The front end validation would work and it would create a token fine but the backend would not accept that token.
So using US did not work anymore but United States worked.
I ended up building a dropdown from this list: https://docs.recurly.com/docs/countries-provinces-and-states
I am trying to create a Google Assistant for my Raspberry Pi in Kotlin. I implemented a OAuth flow using the so called "device flow" proposed in this IETF draft, since my Raspberry shall later just expose a web interface and does not have any input devices or graphical interfaces.
Google does support this flow (of course) and I obtain a valid access token with user consent in the end. For testing purpose I also tried a default authorization flow that will just forward the user to localhost, as it is normally done but it did not solve the problem.
I tested the access token using this tool and it confirmed validity of scope and token. So the token itself should work.
Scope is: https://www.googleapis.com/auth/assistant-sdk-prototype as documented here
This actually does not point to any valid web resource but is referenced in every documentation.
Then I tried to stream audio data to the assistant SDK endpoint using the gRPC provided java stubs. As took a third party reference implementation as a guide how to authenticate the rpc stub. But neither the reference implementation nor my own one works. They both report
io.grpc.StatusRuntimeException: UNAUTHENTICATED: Request is missing required authentication credential. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.
The stub is authenticated this way:
embeddedAssistantStub.withCallCredentials(
MoreCallCredentials.from(OAuth2Credentials
.newBuilder()
.setAccessToken(
myAccessToken,
myAccessTokenExpirationDate))
.build()))
and the authenticated request is performed like this:
val observer = authenticatedEmbeddedAssistantStub.converse(myStreamObserverImplementation)
observer.onNext(myConfigConverseRequest)
while(more audio data frames available) {
observer.onNext(myAudioFrameConverseRequest)
}
observer.onCompleted()
(I prefixed pseudo variables with "my" for clarity, they can consist of more code in the actual implementation.)
I even contacted the author of this demo implementation. He told me, last time he checked (several months ago) it was working perfectly fine. So I finally ran out of options.
Since the client implementation I took as reference used to work and I do actually authenticate the stub (although the error message suggests the opposite) Probably, either my valid access token with correct scope is not suitable chosen for the assistant API (though I followed the suggestions of google) or the API servers had a change not properly documented in the getting started articles by google.
So: Did anyone ran in the same problem and know how to fix it? I have the project on github. So if anyone needs the broken source code, I can do a temporary commit that produces the error.
Note, to save some works for mods: This issue referres to this and this question, both unresolved and using different languages but describing a similar problem.
Well, seems I was right about my second assumption: The error is server side. Here is the github issue, let's just wait for the fix.
https://github.com/googlesamples/assistant-sdk-python/issues/138
I am trying to connect to Jira using OAuth. I have followed this manual and I have created app link in Jira instance and configured it with proper consumer key and public key. When I try to request a token using code from the example I am getting 401 with following message (same for python and perl instance):
oauth_problem=consumer_key_unknown
I am out of ideas what can be wrong. I will appreciate any tips.
Well, I believe that I have configured Application link in the wrong place. I have been somehow navigated to the link wiki/admin/listapplicationlinks.action. Then I accidentally found plugins/servlet/applinks/listApplicationLinks which looked pretty much the same as first but content was different. I have added link to the second location and everything works well now. Sorry for confusion.
I also had this similar error. So I then used different "consumer key"(tried to make this unique) other than the given one in the example manual. After searching a lot in internet about this error, I got to know that as most people are using that same consumer key(given in example manual), a database error occurred due to which this error was thrown.
I'm trying to use the FedEx API to track packages. I can authenticate to their test server successfully (using my user credentials, account number, and meter number). However, I receive the same unhelpful response for most tracking numbers that I use in my requests; both test tracking numbers (like 999999999999) and real tracking numbers (that work well on the FedEx website) return the following:
Error Code 9040.
No information for the following shipments has been received by our system yet. Please try again or contact Customer Service at 1.800.Go.FedEx(R) 800.463.3339.
The only requests that fetch a different response are the clearly invalid ones, like "test", which returns:
Error Code 5508.
Invalid tracking number.
I tried SOAP requests using their wsdl (TrackService_v5) as well as manual non-SOAP HTTP POST requests, but their responses are exactly the same in both cases. Is something wrong on their side, or am I doing something wrong?
It seems that FedEx has disabled any test tracking numbers, in the past 999999999999 would work just fine, but now that doesn't even work. To the best of my knowledge, the only way to resolve this is to move to production. Which IMHO is bad because you have to test the tracking part of your application until you move to production.
999999999999 worked for me, but I think I am already in production environment.