Couchbase Lite in fatjar on heroku throws execption on Couchbase.init() - heroku

I am facing a problem which only occurs after uploading and executing my jar on heroku. Simply locally it works but online on heroku on execution the application immediately fails because of the Couchbase.init() command which throws (only on heroku) the following exception. What is the real reason behind it, can I fix it or is there any workaround?
Error

CouchbaseLite for Java and Android are bindings for a library written in C/C++
You have built a Jar file that either does not contain the native library, or cannot install it on your system.

Related

Google Cloud SDK-based Maven plugin is forcing itself to update and then failing, when cloud sdk is up to date

I'm making a Java program which will be deployed to the Google App Engine and I'm using the Cloud SDK maven plugin version 2.4.0 to deploy to the GAE. However when I run mvn package appengine:deploy the cloud SDK will say its current version is 321.0.0 and needs to update to 327.0.0. The update will then fail with the error:
ERROR: (gcloud.components.update) Access is denied: [C:\Users\jamie\AppData\Local\Google\ct4j-cloud-sdk\LATEST\google-cloud-sdk.staging\platform\kuberun_licenses\LICENSES.txt]
However when I just run gcloud components update I get the result of All components are up to date.
Anyone know why this may be happening or how to fix it?
EDIT: As a work-around I found you can force the maven plugin to use a specific version of the sdk by using <cloudSdkVersion>321.0.0</cloudSdkVersion>. I'm still very curious to know why this occurred though
Manged to fix this by deleted the whole C:\Users\jamie\AppData\Local\Google\ct4j-cloud-sdk folder as this forces the plugin to redownload a fresh SDK.
The error occurs as the plugin uses its onw auto managed SDK rather than the one which is user managed.

How to use ServiceCore framework from salesforce in a Xamarin forms app?

I am getting a warning in my console when I try building the app in Release configuration. The warning reads The ServiceSDK frameworks have not been prepared for release.
Please ensure the "prepare-framework" script is run after the "Embed Frameworks" build phase.
From the documentations, I understand that a build phase script has to be run to fix the issue.
Here is how I use the framework in my solution:
I am creating a binding library which refers the framework through a Native Reference. Then I run the library project and build a .dll with I use in the iOS project within my Xamarin forms application. All this is working fine. I am able to use the intended features from the framework.
However, there is this warning which appears in the console when I run the App in Release configuration. Also, when I tried submitting the App to App Store, it throws error, which is apparently the same mentioned above.
I tried by adding Custom commands which I think is the equivalent of Xcode build phase scripts, but the warning doesn't simply go away.
Any help would be really appreciated.
Sample Repos - https://github.com/XamarinUniversity/ENT302
Youtube Video Link - https://www.youtube.com/watch?v=HEypPXVoYnY&feature=youtu.be
Gudie Here - https://xamarinuniversity.github.io/ENT302/

Nativescript sidekick error during cloud build

I am getting a strange error from sidekick cloud build since a few hours ago.
I was building the app successfully, but all of a sudden, it gives me the following error and even reversing the changes does not fix anything. I have even tried with a fully working version of my git repo.
[19-01-28 16:55:27.709] Build step started.
[19-01-28 16:55:37.465] (CLI) Unable to apply changes on device: a754d27bafb8bb273e444b9d6cefd370cd55f4d4. Error is: Build failed..
[19-01-28 16:55:37.469] Error detected during LiveSync on a754d27bafb8bb273e444b9d6cefd370cd55f4d4 for C:\Users\Afshar\Desktop\myapp. Error: Build failed.
I doesn't give me any more details about the issue.
I was wondering if anyone knows how to get more logs in cloud build or if this is a known issue?
Thanks
It happens with me as well for reasons unknown. I couldn't find any root cause, but I did notice one pattern. It usually happens when I am already running the app on an Android Emulator/Device.
When we execute tns run android --bundle, it listens for file changes after the first build and does some webpack incremental build thing afterwards, right?
At the same time, once Sidekick delivers a successful iOS build, it also starts listening for changes to do the webpack incremental builds on iOS.
So while we have these two LISTENERS active and we request for another iOS cloud build, before Sidekick communicates with the cloud, it modifies some files which the android listener detects and results in an incremental android build, which in turn modifies some other files, which the iOS listener detects, resulting in Sidekick trying to do the incremental iOS build but this time its stuck between giving you the incremental update and the new requested cloud build, so it throws you this LiveSync error.
Moral of the story: Try to request cloud builds, when these listeners are inactive.
I finally managed to solve it.
In case anyone else faces this issue, I tried the following command using a hint on this page and it solved the problem.
https://docs.nativescript.org/troubleshooting
tns platform remove ios
and then, I was able to build the project in sidekick.

Ionic 2 has exception when building android - cannot resolve gradle

I am a greenhorn to Ionic (ionic 2.2.3 and Cordova 7.0.1) and run into an exception when trying to build on android as below,
Since my site is behind proxy server, I added a gradle.properties to the folder (C:\Users\.gradle) like below, but get the exactly same error.
I was just wondering how to solve the network issue of gradle or use local gradle.
This might help. Seems like quite a similar issue.
https://software.intel.com/es-es/forums/intel-xdk/topic/595059

WebObjects Unsupported major.minor version 49.0 error

I have been asked to update some old code I worked on years ago. All in xCode no eclipse and the change is needed urgently so do not have time to migrate away from xCode ATM.
I got my hands on a OS 10.5.8 box installed xcode 3.1.4 and the code compiled fine locally.
Tried to deploy never worked " Unsupported major.minor version 49.0 error" seems the server is running JVM 1.4.2 I have 1.6 locally. I followed some instructions on how to downgrade my local machine to java 1.4.2 without success.
So I gave up and put an old copy of the site back on the server. But now ALL the sites on the server get that same error message and none of them will start even though they have not been touched in 3-4 years. Not sure what happened? my only logically explanation is i accidentally did one action on the server instead of locally? Either way I have no idea what is wrong or how to fix it?
Where do I start trying to debug this?
Can I install a new version of java 1.5 or 1.6 on the server (OS 10.3.9) and have it work ok with webobjects?
Was this project a framework or an Application? If it is a framework that is depended-on by the other WebObjects projects, that would explain why everything started failing when you updated this project.
By default, Xcode did not include (or "embed") any depended-upon libraries or frameworks in the Project.woa bundle. Apps built this way depend upon any required resources being available in a few specific locations and then load them at launch. If they all now link to a framework or library that is incompatible, then they'll all stop working.
As far as the actual "Unsupported major.minor version" error goes, you do not need to downgrade the version of Java on your Mac, you can simply tell the compiler to target an older version of Java.
I can't remember if Xcode used Ant to do its Java compiling, but if it did and you are using Ant 1.7 or later, you can force Ant to compile 1.4-compatible binaries with Java 1.6 by editing the build.xml file so the javac tag includes a "target" parameter such as: <javac target="1.4" ... /> or by passing in the ant.build.javac.target property when you call Ant, either via command line or by modifying a properties file that Ant will load. I believe build.properties still existed in Xcode-based WebObjects projects. If it does this would be a good place for the property.
The basics are covered by this stackoverflow question: How to compile classes to JDK1.5 when ant is running in JDK1.6

Resources