-
-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue of cordova.plugins.emiAdmobPlugin.requestIDFA() #57
Comments
I don't have iphone/ipad, I'm a poor person can't buy expensive phone, what else iphone/ipad with IOS 14 + To test it on a real device.
example
|
this condition also applies or is the same as data.attStatus |
@EMI-INDO Test 2: In my reported bug, IDFA explainer message (dialog 1) has not showing in real device. |
|
1:Make sure your application has completely finished loading, displayed to the main page of the application, then call the function requestIDFA 2:you can try adding a little pause before the requestIDFA function is called. 3:Solving this problem will be a little difficult because I don't have the original iphone device🙏 |
|
I meet 3 issues of using cordova.plugins.emiAdmobPlugin.requestIDFA().
Env is: Capacitor 6.0 + IOS 18.2.1 + Xcode 16.2 + 2.0.5 version
When execute "cordova.plugins.emiAdmobPlugin.requestIDFA()", no IDFA explainer message showed in real iphone device. But it can showed in virtual xcode simulator. When we has done some IDFA configure in Admob, the IDFA explainer message shoule come after we call this function.
The iOS ATT Alert come first than IDFA explainer message in xcode simulator. According to Admob document, the order should be as following:
We should get explainer message firstly.
3.Different behavior in real device with simulator. If we create a IDFA expaliner message in Admob, then we do not call cordova.plugins.emiAdmobPlugin.requestIDFA(). Yes, do not call this function! We could get a right order in simulator. IDFA explainer message comes firstly, then show ATT alert. However, we will get nothing in real device. This is not a right behavior.
The text was updated successfully, but these errors were encountered: