I am getting problem in web smooch widget.
Here is complete question posted in git repo.
https://github.com/alavers/smooch-bot-example/issues/40
The version of Web Messenger you are using was deprecated in Summer 2017 is no longer supported. You'll need to update to a version > 4.0.0 in order to keep using your integration. Installation instructions can be found in the documentation. See the v4.0.0 release notes for notable changes when switching from the 3.x version series.
Note also that the GitHub repository you linked is not an official Smooch repository and is not actively monitored for support requests.
Related
Currently I am going to verify FIWARE.
Release 7.5 was announced, but there are components whose version is lower in the core component.
cygnus
Release7.4 : version2.0.0
Release7.5 : version1.9.0
sth-comet
Release7.4 : version2.4.0
Release7.5 : version2.3.0
I want to know the reason why the version of the component is going down.
With regards to Cygnus, the short history is that FIWARE wrongly used "Cygnus" as software name in FIWARE 7.4 for a component that in FIWARE 7.5 was renamed to "Draco". Cygnus stills existing of course but release 2.0.0 has not come yet. Last Cygnus available version in the moment of writting this is Cygnus 1.10.0, to be included as part of FIWARE release 7.5.1.
With regards to STH, probably FIWARE releases are still using this fork as reference, when it should be using the original one. Note the original repository is the most updated and the one which uses version 2.4.0 at the present moment.
#fgalan is correct, some elements were inconsistently labelled in release 7.4 and 7.5. A patch release has finally corrected this.
As of 7.5.1, the following versions are correct:
cygnus 1.10.0
sth-comet 2.5.0
draco FIWARE_7.5
The new draco generic enabler had been initially released as cygnus 2.x which was incorrect.
I'm trying to replicate the installation guide to integrate Wirecloud 1.0.1 with the latest version of IDM Keyrock.
I'd like to understand if the guide in the documentation is valid again for this version of WC.
Thanks in advance for the answers.
As you suspected, the linked documentation is not valid for WireCloud v1.0.1, you linked to the latest branch of the documentation, that is the documentation for the development version of WireCloud.
The documentation on how to configure WireCloud v1.0.1 to use the IdM can be found in this link.
We know that is not clear that the latest branch is the one used for document the development version, but Read The Docs does not allow us to rename (or we do not know yet how to do it) this branch using a more meaningful name (e.g. develop). The default branch is stable (pointing to the documentation of the latest stable version of WireCloud) but it has proben to not be enough. We have created a ticket for improving this aspect.
I am installing the orion pep proxy but I think that I have not downloaded the correct version and I am having errors when using a local instance of KeyRock to validate and generate tokens.
I know that the latest version is 0.6.0 but i do not know how to complete the following command to obtain the last version:
./create-rpm.sh
Which is the difference between version and number?
Could you help me with this?
Thanks in advance
The idea of having those two numbers is to help the Release Engineer in debugging their releases, or changes they make to the packagin process itself. The "release number" indicates the version of the package, not the one of the software. E.g.: if you are packaging version 0.6.0, you usually will use release number 1; but, if you find out that you want to add some dependencies for the spec, or you want to update the package to change part of the packaging process, for example, and you try to replace the installed version with a new one, the system will claim the package is up-to-date; in that case, you increase the release number (as the software itself, that is, the Node.js files that constitute the PEP Proxy) hasn't change.
Hope this clarifies the behavior.
The current SharpCompress.WindowsStore.dll library published on Nuget is build in Debug mode. I got this error from the Windows Store App Certification Kit.
Error Found: The debug configuration test detected the following errors:
The binary SharpCompress.WindowsStore.dll is built in debug mode.
Is there any way to have/compile the SharpCompress lib in Release Mode?
I'd rebuild it in release mode.
What, you didn't think about that?
It's on NuGet, right? NuGet packages often list a project site. So looking at the page I can see the link points right over here. That's on GitHub. That's where source lives.
You can either fork it (which there isn't really a point, since you don't want to develop it), clone it (aka use a Git tool such as GitHub for Windows) to your local machine, or just download the latest code in a zip file.
From there you can build in release mode and away you go. May not be just that easy, as there might be some dependencies or such that need resolving. Now off you go.
I go http://developers.box.com/onecloud/ to download the Android SDK. I got box-box-android-sdk-5482811 Is this the latest version?
Because when I open up the OneCloudAppToAppSample, even the R. variable is not well defined. And I cannot run the sample code.
Where can I find more help or documentation on using Box with Android SDK?
The SDK is being improved quite frequently, so our advice would be to always use the latest version on the "master" branch. We consider the master branch to be our stable release. In your case, 5482811 should work fine.
Regarding your issues with the sample app, I don't seem to have any problems compiling it off of a fresh download. I can think of one thing you might be running into:
The sample app was configured to point to target "Google APIs:15". It's possible you don't have this installed (through the Android SDK manager). We actually should not have configured this build target, since the project doesn't use the Google APIs, and we'll fix that in our next release.
In the meantime, could you try this (assuming you're using Eclipse):
Right-click on the OneCloudAppToAppSample project and go to Properties.
Go to the Android section on the left, and change the build target to Android 4.0.3 - 15 (not the Google APIs version).
Project -> Clean -> Clean all projects.