Before 1.2.0 I am using 1.0 version and it was working fine but after the update, the new version 1.0 to 1.2.0 and there is some changes in callback URL like getting to Post. I have made all the changes and I can able to the call back URL is triggering from XMPP server but it was not calling my server side.
I can able to see logs till line 112:
Xmpp File
After 122 logs are not showing in XMPP log.
Can anyone have done the CallbackOnOffline 1.2.0?
Please help me out with the problem.. if anyone has a solution about it.
Thanks in Advance!
I am facing same issue with 1.2.0 version, so I am suggesting you can use old version 1.0 instead of 1.2.0 for now.
CallbackOnOffline.jar 1.0
Let me know if it will not works.
Related
I am using the latest unity SDK 2.12.0 and Unity 2017.4.
My unity project is available here:
https://github.com/jignesh015/Watson_trial
Please note that you will need an IBM Apikey to access the API functionality.
I followed the following video tutorial for setting up the SDK:
https://www.youtube.com/watch?v=_K62R9Jnxag
While running the ExampleStreaming sample as shown in the video, I'm getting the following log:
[SpeechToText.SendStart()][DEBUG] SendStart() with the following params: {"action":"start","content-type":"audio/l16;rate=22050;channels=1;","inactivity_timeout":-1,"interim_results":true,"max_alternatives":0,"profanity_filter":false,"smart_formatting":true,"speaker_labels":false,"timestamps":true,"word_confidence":true
[SpeechToText.OnListenClosed()][DEBUG] OnListenClosed(), State = DISCONNECTED
[SpeechToText.KeepAlive()][DEBUG] KeepAlive exited.
I have thoroughly searched for this issue. Seems like many people have faced a similar issue, but none of the posts have a satisfactory solution. Can anyone help me with this?
This has to do with the move to TLS 1.2. Only Unity 2018.2 and above support TLS 1.2 using .NET 4.x equivalent Scripting Runtime Version. https://github.com/watson-developer-cloud/unity-sdk#streaming-outside-of-us-south-region
Since you are using Unity 2017.4 you will need to create your Speech to Text instance in US South (Dallas). This is the only region that still supports TLS 1.0.
Alternatively, you can update to Unity 2018.2 or above and switch to Scripting Runtime Version .NET 4.x equivalent.
Supposedly, twilio handles encoding automatically... but it doesn't.
My code is as in the tutorial:
String msg = "áéíóú";
Message message = Message.creator(new PhoneNumber(toNumber),
new PhoneNumber(fromNumber),
msg).create();
But in the phone, the message arrives with the infamous � characters
I have tried changing the JVM locale parameters:
-Duser.language=es -Duser.region=MX
to no avail
I'm testing in a Linux box. On my colleague's Windows 10 box works fine.
Any pointers?
I just ran into this issue and currently have a ticket opened with Twilio Support on this.
I took a chance and tried the previous version of their API and it worked without a hitch.
Use maven to grab the 6.3.0 version of their Java API or download it from their Java API Page however they note that version 6.x is deprecated. Hopefully this will be addressed in an update to their API.
Example Code for sending Messages with the 6.3.0 version of Twilio's Java API
I have a REST API that was working with Jersey 2.6 and Swagger 1.3.7. I read that Jersey 2.9 fixes a warning that I was getting so I upgraded to the latest Jersey 2.16 but then Swagger stopped working. I went back and upgraded one version at a time until I saw that Swagger was working with 2.15 so I settled on that. Now, the PUT API fails with Swagger with the following error:
The server refused this request because the request entity is in a format not supported by the requested resource for the requested method
The API works using FireFox RESTClient and specifying "application/json".
I do have "jersey-media-json-jackson" as a dependency and call "Client client = ClientBuilder.newClient().register(JacksonFeature.class);" in the program.
I tried upgrading Swagger but that did not help.
Has Swagger been verified to work with Jersey 2.15/2.16?
I've recently managed to get swagger-core to work with Jersey 2.16 with a similar issue. Keep in mind they are using the latest version (1.5.X) and not 1.3.X but the same solution will apply.
The problem is most likely with version resolution, specifically, the one of jackson-databind. For some reason, even jersey-media-json-jackson 2.16 depends on an older version of jackson-databind, even though it works fine with the latest version. Without having more details, it would be difficult to suggest a full solution, but you can follow the dependency tree and see the conflicts there.
If you do require further assistance, I'd suggest either using our mailing list, or even better, the IRC channel where we could interact online and resolve it.
Im in the process of evaluating the new interface of Apache Archiva. The user interface is really good and I was able to configure most of the settings.
However, when I try to deploy the artifact through eclipse Im getting the below error.
Error code 405, HTTP method PUT is not supported by this URL
I donot get this when I use the Apache Archiva 1.3.6.
Any idea?
This can happen if your repository URL is incorrect. See GitHub issue 4.
I have setup the new Archiva version 2.0.0. Apparently this issue has been fixed with the latest version.
as the question says, i'm trying to connect to the socket.io server from an app running on iphone/ipad.
in another Q i found the link to achieve this with the help of
https://github.com/fpotter/socketio-cocoa
... buuuut. it's not working anymore (socket.io 0.7.2).
error messages i get are:
socket.io
warn - unknown transport: "undefined"
client
Connection failed with error: The operation couldn’t be completed. (WebSocketErrorDomain error 1.)
downgrading socket.io to version 0.6.17 works but i still want to try and get this up and running with the newest version.
maybe someone can point me in the right direction what changed w/ 0.7.2 so i can fix the socketio-cocoa classes (or these https://github.com/erichocean/cocoa-websocket - because socketio-cocoa relies on them).
thx
i took the time and tried to implement the new protocol starting with the v.0.7.2.
not everything done yet but there's a rough first draft with which you can work.
rooms are still missing, because i don't need them right now - but feel free to add them yourself ;)
here is the github link socket.IO-objc. it's loosely based on the version from fpotter but because i changed some stuff and the two version are not compatible, mine got a different name and new repo.
Socket.IO 0.6 API & protocol is not compatible with a 0.7 server.
The cocoa classes are still using the 0.6 protocol. The 0.7 protocol specification can be found here: https://github.com/LearnBoost/Socket.IO-spec
So the only 2 options you have are:
Downgrading your server to 0.6
Contributing to the third party cacoa project and update it to the 0.7 protocol