Agora.io websdk example gives error ERR_DYNAMIC_USE_STATIC_KE - agora.io

I am following sample example from
https://github.com/technophilic/Agora-demo-web
When I run it with "live-server" it gives following error:
Agora-SDK [ERROR]: User join failed [ERR_DYNAMIC_USE_STATIC_KE]

Refer to the following link for the solution to your issue.
https://docs.agora.io/en/faqs/token_error#120-dynamic-user-using-the-static-key
Contact us for any further assistance.

Related

Datastream Troubleshoot: "An unknown error occurred. Please try again. If the error persists, contact Google support"

We are trying to replicate data from AlloyDB to Bigquery using Datastream.
We Get "An unknown error occurred. Please try again. If the error persists, contact Google support."
In the Datastream console --> objects list, we see all source tables with Object Status "Failed" and Backfill status "Completed".
In Bigquery we see only a subset of the tables (not all the "Completed" objects were synced).
In the Logs Explorer I can see this error on BQ:
I also see this error: error: {
code: 11
message: "Unsupported primary key column either does not exist or is a pseudocolumn at [1:401]"
}
The column referred in the error is of type enum.
The desired situation is having all the AlloyDB tables replicated into Bigquery.
The error message is not very informative...
What does it mean?
What would be the best way to go about troubleshooting this?
We're actively working on making these error messages be more informative, and improvements are continuously being rolled out as we identify more edge cases. Assuming you followed all the steps in the documentation, then you may need to open a ticket with support for further investigation. If a support ticket isn't an option, you can still report the issue using the public issue tracker
I just had this same issue but connecting to a PostgreSQL in AWS RDS:
Beginning with Postgres 10, passwords are encrypted using SCRAM-SHA-256 in PostgreSQL. Google DataStream still expects MD5 password encryption, or it will generate an "unknown error" in the logs and fail the backfills.
You'll need to update your postgresql.conf (or RDS Cluster Parameter Group if you're using AWS like me):
password_encryption = 'MD5'
Restart the database and make sure the parameter has changed with:
SHOW password_encryption;
Reset the password of your users:
ALTER USER "{username}" with password '{password}';
More info from the PostgreSQL docs: https://www.postgresql.org/docs/current/auth-password.html

yowsup-cli: registration procedure failing, something unknown is "missing"

I am using yowsup-cli, and it prints the following when I run "yowsup-cli version" ...
yowsup-cli v2.0.13
Using yowsup v2.4
I am trying to perform the registration as specified in the yowsup documentation, as follows. However, it fails.
First, I entered this command, and I indeed got a code back via SMS ...
yowsup-cli registration --requestcode sms --phone 1XXXXXXXXXX --cc 1 --mcc 310 --mnc 260
I then entered this command using the code I got back (shown as "AAA-BBB"), but it failed ...
yowsup-cli registration --register AAA-BBB --phone 1XXXXXXXXXX --cc 1
This is the error message I received ...
status: fail
reason: missing
What I did above is exactly what is described in the yowsup documentation, here: https://github.com/tgalal/yowsup/wiki/yowsup-cli-2.0#yowsup-cli-registration%29 (see the commands listed under "Example:").
Note that I get the same failure when I add the MNC and MCC info to the "--register" command.
Does anyone know why this registration procedure is failing, and what might be "missing" in what I'm doing?
Note that the MCC and MNC I specified are what I found when looking up my cell provider (T-Mobile, USA).
Also, note that I am able to run WhatsApp with no problems from my mobile device, as well as via their web interface.
Thanks for any help and suggestions.
you do not have to put "-" in your otp/code. it will be a plain sms code
yowsup-cli registration --register AAABBB --phone 1XXXXXXXXXX --cc 1
i hope it works

DAG provider returns refresh error code 517

Our team can't use the DAG right now.
When trying to add an item with the provider DagBankSeCUrityQA - Bank (14748) I get a refresh error code 517.
Example itemID: 15466424
Please assist.
Thanks,
Michael.
If you are still getting this error let us know, it seems like you might be getting this error due to some temporary issue during that time.

Application Cache Error

I've got this error:
Application Cache Error event: Manifest fetch failed (-1)
http://localhost:8080/offline.manifest
online: NO, event: error, status: idle
This JSON String show the content of the error:
({"returnValue":true,"eventPhase":2,"timeStamp":1355923608009,"target":{"onprogress":null,"onchecking":null,"onerror":null,"onupdateready":null,"oncached":null,"ondownloading":null,"status":1,"onobsolete":null,"onnoupdate":null},"type":"error","cancelBubble":false,"cancelable":false,"defaultPrevented":false,"srcElement":{"onprogress":null,"onchecking":null,"onerror":null,"onupdateready":null,"oncached":null,"ondownloading":null,"status":1,"onobsolete":null,"onnoupdate":null},"bubbles":false,"currentTarget":{"onprogress":null,"onchecking":null,"onerror":null,"onupdateready":null,"oncached":null,"ondownloading":null,"status":1,"onobsolete":null,"onnoupdate":null}}) debug.js:34
I got it with JSON.stringify(error).
OK I have this information. But what can one understand from here???
Where is the problem? How can I solve it?
Thank you in advance.

Error 22 when scanning for available WiFi-Networks using CoreWLAN

I use the following code to scan for all available WiFi-Networks:
[[CWInterface interface] scanForNetworksWithSSID:nil error:&err];
Usually I get a NSSet of Networks but sometimes I get the following error:
The operation couldn’t be completed. (com.apple.coreWLAN.error error
22.)
Error Domain=com.apple.coreWLAN.error Code=22
I haven't find anything about that error code 22. Is there a documentation or a solution for this?
Because I had another problem with CoreWlan(http://stackoverflow.com/questions/9943833/cwinterface-returning-no-data) i replaced it with Apple80211.framework.
This also is a workaround for this one...