Hi guys,
I tested my app on new daily build that support 64bit and got console errors about self hosted plugins.
plugin.adjust: ERROR: Self-Hosted plugins was not activated.
@Rob can you please discuss this with relative person in your team? Thanks
Regards,
Usman Mughal
Self-hosted plugins are actually a privilege that we have to turn on in our developer portral (which you have), but the new builds are validating against the Marketplace licenses, which is something new. I’ve gone through and granted Marketplace Licenses to match the developer portal licenses. You should be able to try again and see if you can get passed this error.
Rob
@RobMiracle Can you enable self-hosted plugin on my account? I should have the license to the self-hosted plugins, but with the new build, we are encountering this error.
You should be setup already. I took care of granting the change needed for the new Android builds yesterday. Are you still having issues? Everything looks right on my end.
Rob
Hi Rob - Here is a screenshot of the error we are getting, along with a screenshot of if we were to go to the marketplace, we can confirm that we have the self-hosted plugin option.
The problem is that “Self Hosted Plugins” is a service, not an actual plugin. I’ve given you a “license” to it, but since it’s not a plugin, I’m not sure how we validate against it. Previously, builds checked against a setting in developer.coronalabs.com, not marketplace.coronalabs.com.
I’ll speak with Engineering. If this isn’t working, we may have to make a fake plugin.
But regardless, since I need to know what email address you’re authenticating against in the Corona simulator and making sure you’re using the same email address in Marketplace, lets take this to support@coronalabs.com so that we are not exposing your email address here in the forums.
Rob
I think we figured out the problem. Try it again.
Rob
Hi Rob, I tried now but this time error is different. Please find the screenshots attached.
Error don’t guide the issue. Is it something related to plugins code or still something on your side?
Regards,
Usman Mughal
I’m using the account that has self hosted plugins activated.
Is plugins.jar your plugin?
What plugins are you using?
Looks like the issue is with one of our self-hosted plugins, our Amplitude.com plugin. We do have another self-hosted plugin that seems to be working fine.
[quote name=“usmanmughal.uog” post=“399943” timestamp=“1562662265”]Hi Rob, I tried now but this time error is different. Please find the screenshots attached. 
Screenshot 2019-07-09 at 8.55.52 AM.png Screenshot 2019-07-09 at 8.56.13 AM.png Error don’t guide the issue. Is it something related to plugins code or still something on your side? Regards, Usman Mughal [/quote] Might seem unrelated and probably actually is but you might want to try adding an admob Id and try again. We had almost the exact same errors while building our apps and we dont even use admob but some other ad networks still seem to rely on the app id so might be worth a tryhttp://docs.coronalabs.com/plugin/admob/index.html#project-settings
It’s really helpful to do copy/paste instead of screenshots of your console log.
Secondly, please, post your build.settings (again copy/paste and/or use pastebin)
Rob
From what I can see from screenshots it seems like you’re including some Google’s libraries as JARs, which is not supported (or correct thing to do).
For example, Vungle’s plugin used to include support-annotations-27.1.1.jar, support-compat-27.1.1.jar and support-core-utils-27.1.1.jar and other files from shared libraries. Deleting those files and using shared dependency plugins helped similar issue.
Also, there is new dependency, which isn’t documented yet: “shared.google.play.services.ads.identifier”, because “shared.google.play.services.ads” after update to 17+ requires admob identifier.
It is really hard to tell what is wrong in your private plugin setup without seeing it.
I’m closing this thread. Self hosted pluins are supported. If you need help with particular plugin self-hosted plugin, let me know. You can PM me here or on Slack
Self-hosted plugins are actually a privilege that we have to turn on in our developer portral (which you have), but the new builds are validating against the Marketplace licenses, which is something new. I’ve gone through and granted Marketplace Licenses to match the developer portal licenses. You should be able to try again and see if you can get passed this error.
Rob
@RobMiracle Can you enable self-hosted plugin on my account? I should have the license to the self-hosted plugins, but with the new build, we are encountering this error.
You should be setup already. I took care of granting the change needed for the new Android builds yesterday. Are you still having issues? Everything looks right on my end.
Rob
Hi Rob - Here is a screenshot of the error we are getting, along with a screenshot of if we were to go to the marketplace, we can confirm that we have the self-hosted plugin option.