I have tried to setup the APM SDK however when I try to run my application I get the following error message:
I/com.huawei.agc.apms: failed to fetch remote config: client token
request miss client id, please check whether the
'agconnect-services.json' is configured correctly
I found https://forums.developer.huawei.com/forumPortal/en/topic/0203417432150160006 which talks about this error.
I found that I had missed the (Rather important) step of actually applying the required plugin in my app level build.gradle file
Adding:
plugins {
id 'com.android.application'
id 'com.huawei.agconnect'
id 'com.huawei.agconnect.apms'
}
fixed the issue
Related
E/FirebaseInstanceId( 8475): Failed to get FIS auth token
E/FirebaseInstanceId( 8475): java.util.concurrent.ExecutionException: com.google.firebase.installations.FirebaseInstallationsException: Firebase Installations Service is unavailable. Please try again later.
I am facing this problem. Because of this firebase messaging is not working. I am facing this error on the my live app also.
I tried to:
flutter clean
Build project again
redownloaded the google-services.json file
Tried to change the firebase dependencies.
"But it didn't work".
I've setup Firebase App Distribution for my Flutter Project and it works perfectly local. But if I try to run it on Codemagic I get teh following error:
Error: failed to fetch app information. HTTP Error: 403, Firebase App Distribution API has not been used in project XXX before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/firebaseappdistribution.googleapis.com/overview?project=XXX then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry.
The XXX are placeholders for a project ID. But I have no Project with that I. If I open the url I get a message that I'm not justified.
Here is my fastlane command:
lane :deploy_dev_firebase do
firebase_app_distribution(
app: "***330f",
testers: "***#gmail.com",
release_notes: "release",
firebase_cli_path: "/usr/local/bin/firebase",
apk_path: "../build/app/outputs/apk/dev/release/app-dev-release.apk"
)
end
And my codemagic Post-build script:
#!/bin/bash
gem install bundler
cd android
bundle install
bundle exec fastlane deploy_dev_firebase
Fastlane builds a bundle and I can upload it manually, but if I run
upload_to_play_store(
track: 'internal',
package_name: "package-name",
skip_upload_apk: true
)
it throws the following error:
Google Api Error: apkNotificationMessageKeyBundleRequiresPlaySigning:
For uploading an AppBundle you must be enrolled in Play Signing.
The Play Signing is enabled, I released a version after I enabled it. What may be a reason for the error?
Enrolling in the new singing option through Google Play Console would be best.
I am building a Domo custom app and the domo auth process is managed by the npm package ryuu. When launching my app locally, I get this error:
error: {status: 401, statusReason: "Unauthorized", path: "/domoapps/apps/v2/contexts", message: "Full authentication is required to access this resource"}
I have ADMIN rights in my Domo instance, so this should not be the problem. How to I fix this ?
Ok I found a temporary fix: ryuu was in version 3, I uninstalled it and reverted it to version 2:
npm uninstall -g ryuu
npm i -g ryuu#2.23.22
The login process now happens in the CLI and not through the web interface which seems to make a difference. This needs to be fixed in version 3.
The Domo Dojo corresponding feed I opened: https://dojo.domo.com/t5/Domo-Developer/Ryuu-auth-does-not-work/m-p/34372/highlight/false#M935
I am trying to upgrade to Jira 7 from version 6. I used the rapid upgrade method. It installs fine but I get an error on the browser “There is a problem with your Jira Access”. I went through the logs and I see that 6 plugins are failed to load during the Jira startup. Somehow they are disabled. I replaced couple of these .jar files with latest .jar and re-started the service, but I get the same error.
I also ran this query update pluginstate set pluginenabled='true' in the db but no luck.
Here is the log:
net.customware.plugins.connector.salesforce.salesforce-connector-plugin' - 'ServiceRocket Salesforce.com Connector Plugin - Plugin' failed to load.
Cannot start plugin: net.customware.plugins.connector.salesforce.salesforce-connector-plugin
Unresolved constraint in bundle net.customware.plugins.connector.salesforce.salesforce-connector-plugin [206]: Unable to resolve 206.0: missing requirement [206.0] osgi.wiring.bundle; (osgi.wiring.bundle=net.customware.plugins.connector.atlassian.jira-connector-plugin) [caused by: Unable to resolve 204.0: missing requirement [204.0] osgi.wiring.package; (osgi.wiring.package=javax.xml.rpc)]
It was loaded from C:\JIRA_data\plugins\installed-plugins\salesforce-connector-plugin-6.0.8.jar.
We had the same problem last week, upgrading from 6.4.13 to 7.1.6. There are some incompatible plugins that crash Jira 7 when started, despite an apparently successful upgrade. Please refer to this page for details on the target plugins, as well as a way to solve the problem:
https://confluence.atlassian.com/jirakb/upgrading-to-jira-7-throws-a-nosuchmethoderror-on-com-atlassian-crowd-embedded-api-user-781396615.html