flutter Admob LoadAdError(No ad config) - android

I have a error when I used admob.
It gives an error even though I have done all the settings. LoadAdError(code: 3, domain: com.google.android.gms.ads, message: No ad config., responseInfo: ResponseInfo(responseId: null, mediationAdapterClassName: , adapterResponses: [], loadedAdapterResponseInfo: null), responseExtras: {})
Error
AndroidManifest configuration
I made the settings but it didn't work

Related

There was an unknown error with the FCM server. See this error's details for more information

I'm trying to setup Push Notifications Setup and I have followed this documentation for the frontend and backend as well https://docs.expo.dev/push-notifications/overview/.
I have created FCM for android and I have used the API server key in the google-service.json that firebase gave it to me to put it in the project.
When I created the apk(to test the notification) in my logs it showed me this error:
[
{
id: 'c4b19090-cc75-482e-b194-a37647fd2af7',
status: 'error',
message: "There was an unknown error with the FCM server. See this error's details for more information.",
messageEnum: null,
messageParamValues: null,
details: {
error: 'ProviderError',
errorCodeEnum: 1,
fault: 'fcm',
fcm: [Object]
}
}
]
How can I solve this error?

WDIO 6: Getting "Error: An unknown server-side error occurred while processing the command. Original error: chrome not reachable" - v100.0.4896.127

I'm using WebdriverIO 6 with SauceLabs and getting the below issue in Android tests. It fails when we try to switch contexts or if the validation happens after loading through navigation which is mostly consistent. It currently shows the chrome driver version is 100.0.4896.127 but i'm not able to find how to change/update it or check the compatibility.
I tried changing different versions of appium and android but I can see the same issue. Due to project dependencies, I will not be able to update webdriverIO to the recent version(7.x.x) which dropped the support for Node 10. So, I have to try with WebdriverIO 6 as of now.
Current Node version: 10.16.3
Error: An unknown server-side error occurred while processing the command. Original error: chrome not reachable
(Session info: chrome=100.0.4896.127)
[emulator-5554 android 12 #0-5] Error: An unknown server-side error occurred while processing the command. Original error: chrome not reachable
[emulator-5554 android 12 #0-5] (Session info: chrome=100.0.4896.127)
In package.json under devDependencies:
"wdio-chromedriver-service": "^6.0.4",
"#wdio/codemod": "^0.9.0",
"#rpii/wdio-html-reporter": "6.3.1",
"#wdio/appium-service": "6.1.0",
"#wdio/cli": "6.12.1",
"#wdio/jasmine-framework": "^6.11.0",
"#wdio/junit-reporter": "6.11.0",
"#wdio/local-runner": "6.12.1",
"#wdio/sauce-service": "6.12.1",
"#wdio/spec-reporter": "6.11.0",
"#wdio/sync": "6.11.0",
"appium": "1.22.0",
My config looks like
capabilities({
autoWebview: true,
autoWebviewTimeout: 180000,
deviceOrientation: 'portrait',
phoneOnly: true,
maxSession: 5,
deviceName: 'Google Pixel 4 GoogleAPI Emulator',
build: `Test on Emulator`,
unicodeKeyboard: true,
autoGrantPermissions: true,
connectionRetryTimeout: 90000,
appiumVersion: '1.22.1',
app: 'storage:filename',
platformName: 'android',
platformVersion: '12.0',
appPackage: 'appPackage_details',
appWaitActivity: 'appWaitActivity_details',
videoUploadOnPass: false,
recordScreenshots: false,
extendedDebugging: false,
fullContextList: true,
automationName: 'UiAutomator2',
noReset: true,
newCommandTimeout: 180000,
});
Please let me know how to resolve this issue. Any help is appreciated.

Nativescript - FirebaseApp is not initialized in this process

I´m really desperate about this problem. I´m trying to solve this issue for such a long time now, but I just can´t get it working.
My goal is to use Firebase withhin my Nativescript-App, which also uses Angular 7, but every time I try to "begin" using firebase, I get the following error:
Default FirebaseApp is not initialized in this process com.nativescript. Make sure to call FirebaseApp.initializeApp(Context) first.
I already tried that. I followed this tutorial:https://github.com/EddyVerbruggen/nativescript-plugin-firebase
My Nativescript App is build in "Typescript", so I choose the Typescript-way.
Since I don´t have the app.js, I started the .init in app.ts like so:
import * as application from "tns-core-modules/application";
import * as FirebaseApp from "nativescript-plugin-firebase/app"
import { environment } from './environments/environment';
FirebaseApp.initializeApp(environment.firebase);
import * as firebase from "nativescript-plugin-firebase";
firebase.init({
// Optionally pass in properties for database, authentication and cloud messaging,
// see their respective docs.
}).then(
() => {
console.log("firebase.init done");
},
error => {
console.log(`firebase.init error: ${error}`);
}
);
application.run({ moduleName: "app-root" });
When I try FirebaseApp.initializeApp(environment.firebase), it crashes and says in the log:
S: firebase.init error: Firebase already initialized
Successfully synced application com.nativescript. on device 97412f42.
System.err: An uncaught Exception occurred on "main" thread.
System.err: Unable to start activity ComponentInfo{com.nativescript./com.tns.NativeScriptActivity}: com.tns.NativeScriptException: Calling js method onCreate failed
System.err: Error: java.lang.IllegalStateException: Default FirebaseApp is not initialized in this process com.nativescript.. Make sure to call FirebaseApp.initializeApp(Context) first.
System.err:
...
That´s interesting, because above it says "already initialized", but right after that it says "FirebaseApp is not initialized". Okay, so I decide to remove firebase.init({...}) because maybe that´s just too much init, but obviously nope:
System.err: Unable to start activity ComponentInfo{com.nativescript./com.tns.NativeScriptActivity}: com.tns.NativeScriptException: Calling js method onCreate failed
System.err: Error: java.lang.IllegalStateException: Default FirebaseApp is not initialized in this process com.nativescript. Make sure to call FirebaseApp.initializeApp(Context) first.
System.err:
...
Don´t worry, I purposly removed com.native.script.THEID, just in case.
When I decide to replace FirebaseApp.initializeApp(environment.firebase) with the firebase.init-part it also gives the same error.
My environment.ts is in a folder called environment and it´s in the same directory as app.ts (the folder).
This is how environment.ts is looking like:
export const environment = {
production: true,
firebase: {
apiKey: 'THE API KEY',
authDomain: 'THE AUTH DOMAIN',
databaseURL: 'THE DATABASE URL',
projectId: 'THE PROJECT ID',
storageBucket: 'THE STORAGE BUCKET',
messagingSenderId: 'THE SENDER ID'
},
};
I already download the google-services.json from Firebase Console (where you setup your App) and pasted it into app/App_Resources/Android/
Please guys, I really don´t know any further. I even tried the second page of Google Search.
If you need any infos, please let me know.
MY SOLUTION
Unfortunately I had to abandon this project and create a new one with angular-templates.
I must have messed something up while enabling mutliDex since I had struggles enabling it back then.
My theory is that, by messing up the activation of multiDex, I probably create two instances of my app build when I run tns run android.
So, the only solution was to start over again, but at least the Firebase initialization works now just fine!

Google Play Console OnePlatformRpcException

I add a new app and I can't do anything because of the above error on google play console
OnePlatformRpcException: status: code: 13 message: Internal error encountered. , request: RpcRequestz_play.console.apps.api.pricing.PricingService_GetBillableCountries, httpStatus: 500, stackTrace: null
Can anyone come across this problem and solve it? I think this is an error from Google.

GraphMethodException: errorCode: 100, subErrorCode: 33, when using latest Firebase UI Auth release

I'm using Firebase UI (Facebook, Google & E-mail), I was using this dependency for Firebase UI:
implementation 'com.firebaseui:firebase-ui-auth:4.1.0'
But there was a bug so I had to change to:
implementation 'com.firebaseui:firebase-ui-auth:4.3.0'
As it was solved in that release, but when I changed it to that version, it now works on my physical phone only but doesn't work on any emulator (I'm afraid it may not work on other phones), it shows a progress bar only
Now when I run the app using 4.3.0 I get the below error when I use 4.1.0 it works fine, but there are other bugs in 4.1.0 so I can't use it.
Here is the error from the Log:
GraphResponse: {HttpStatus: 400, errorCode: 100, subErrorCode: 33, errorType: GraphMethodException, errorMessage: Unsupported get request. Object with ID 'MY_APP_ID' does not exist, cannot be loaded due to missing permissions, or does not support this operation. Please read the Graph API documentation at https://developers.facebook.com/docs/graph-api}
So does anyone knows why am I getting this response or how to solve it? I think this response should occur if I'm requesting user information, but I'm not requesting any user information, my App Id is the only thing added and being requested.

Categories

Resources