Please provide technical details so we can reproduce the issue.
Nothing else beside upgrading the SDK from 5.7.1 to 6.0.0 version.
I am sure there is something else 
For example, what is the compilation error?
How is the project configured?
What do we need to do to reproduce the problem?
Can you see it?
It actually points a problem within the Backendless SDK only.
Due to using higher level functions, my app can not compile.
I am sure the problem is in yours for using invokedynamic which only supported from api 26.
This will be intriguing as many Android devs try to support lower api.
When I revert back to 5.7.1, the problem is gone.
What version of Android SDK do you target?
Minimum SDK version is 21.
I will wait to see what our product team says about it, but with Android 5 as the minimum version, it seems you try to target a super tiny fraction of the Android market:
I suppose that there may be a problem with a cache. Please update the Android SDK to 6.0.0 and then in the Android Studio:
Build -> Clean Project
Build -> Rebuild Project
File -> Sync Project with Gradle Files
Best Regards,
Maksym
It’s not about that.
I have to position myself where the apps are targeted/deployed, the market, the area, and so on. When I change the minimum version to 26, I will miss all of that opportunity.
Still not working.
I’ve already tried that.
You should not deprecate transaction API in previous SDK version. And you should state clearly the minimum Android version your SDK can support.
It’s a big upset. I hope that the 5.7.1 version can support transaction.
Because its not makes sense, the last time today I tested it worked well, and now its not working.
The compilation failed, nothing to do.
The app is rendered not working for now
Previous version? Common, you started using a feature before it was even announced. The doc clearly states it is a version 6 feature:
We’re going to look into it, but calling it “deprecation” is clearly a wrong term.
Regards,
Mark
Okay. I am waiting.
It should be as easy as setting your SDK minimum version into 21 or lower.
We were able to reproduce it. Investigating what causes the new dependency.
Thanks Mark. Hope to hear another good news soon.
I can say for sure that is due to your new SDK is using invokedynamic (MethodHandle.invoke() etc) somewhere.
Have you found the root cause?
not yet.
Okay…
Good luck.
Hopefully you and the team can find the solution today…
Hi Mark, as you and your team are currently investigating this issue, can we request if the transaction API enabled for lower SDK versions temporarily?