As I'm sure many are aware, admob needed an update to use a newer SDK (7.64+) and this message appears on your admob account if you have apps using an SDK below that version:
Some of your iOS apps require a GMA SDK update To keep ads serving normally and minimize a loss in ad revenue, implement the GMA SDK 7.64.0 (or later) for your iOS apps. And configure the SKAdNetwork in your apps with Google's network ID.
Expo had a PR here that was merged 6 days ago. This should have updated the GMA SDK to 7.69.0. However, when I ran expo upgrade it states that it updated expo-ads-admob,
✅ The following packages were updated:
expo-ads-admob, expo-av, expo-keep-awake, expo-updates, react-native, react, react-dom, #babel/core, react-native-web, babel-preset-expo, expo
but no changes actually take effect. And if I have the newer version (10.0.0) that I manually installed as stated below, it downgrades it to 8.4.0.
When that wasn't working, I then went and manually updated expo-ads-admob to 10.0.0 via npm (also tried yarn) and it looked like the node package was actually updated (checking the CHANGELOG and it has info about 10.0.0).
Still when I build my app with expo build:ios, run the new app, and check my GMA SDK version on admob it is still using 7.55.1.
I have also tried completely removing expo-ads-admob and reinstalling, but the same issue occurs.
Any ideas as to why this is occurring? Is there some other method I should be using to upgrade to the latest commit on expo's master branch?
Appreciate all the assistance in advance and let me know if there is any additional info I can provide.
Additional Info:
SDK Version: 40.0.0
Platform: iOS
Workflow: Managed
EDIT: Received answer from Expo member, see answer below.
You cannot use updated packages if using the managed workflow, it must be bare workflow in order to update module versions manually. Therefore, this admob update won't take place for managed workflows until expo SDK 41 is released.
See expo forum here for more.
Related
I have integrated the electron app with the auto-updater and published the electron app as well. I am able to receive the newer version pop-up and able to upgrade my electron app but when I relaunch the installed electron app the app shows the previous version information and asks to install the newer version again. Any suggestions?
I bumped across your question because I was having the same issue. I was using auto-updater with Quasar framework. Maybe this could help someone else.
Since nsis was configured by default to do the oneClick installations (with predefined rules), it was always installing my application somewhere in users/AppData folders, which I didn't even notice.
The thing I was running over and over again (after successfully auto-updating application) was actually installing the previous version all over again.
To circumvent this issue, I changed nsis configuration to allow users to select their own installation path.
nsis: {
oneClick: false,
allowToChangeInstallationDirectory: true
}
After this, app shortcut was appearing on desktop, which was always running the latest version.
I am working with Speechly API in my react application. In that, I imported PushToTalkButton and PushToTalkButtonContainer from #speechly/react-ui and I have also configured from Speechly Playground it's working fine in Playground. Then I click on the button(PushToTalkButton) in react application it is not capturing my voice and not using the microphone. I tried to find out the problem with ErrorPanel but nothing is showing.
Could you try upgrading to version 1.2.4 by issuing npm install #speechly/react-ui#latest
Earlier versions were inadvertently coupled with a certain version of react-client package and might cause a problem you described.
I am using Google Cloud to deploy my application. I have followed the steps in the documentation for deploying. I deployed early on in my project and it was successful. I then decided to change some files and update some features in my app. For this i followed the documentation for updating a deployment. This update was successful. It had me create the deployment in my Deployment Manager and run the gcloud commands to commence update. When I redeployed with gcloud app deploy, it was successful.
I have since added a couple more lines of code and features in my application. I followed the same documentation for updating a deployment as I had the first time I made an update and it is no longer working for me.
Does anybody have any idea what would be the problem? Again, I was able to successfully deploy, and even update that deployment once by following Google Cloud docs. Now I am having no luck.
Have you been changing the version number? Go to:
https://console.cloud.google.com/appengine/versions?project=< your project name >&serviceId=default
And make sure the version you want is active. Also, you can try:
http://<VERSION>-dot-<SERVICE>-dot-<PROJECT_ID>.<REGION_ID>.r.appspot.com
Example:
https://20200813-dot-myapp.uc.r.appspot.com
if the version number was 20200813 and your appname is myapp and the region is uc
I was working on a minor update to an app already accepted and available in the Apple App Store, and when I uploaded the new version, I got an e-mail that the binary was rejected because:
ITMS-90809: Deprecated API Usage - New apps that use UIWebView are no
longer accepted. Instead, use WKWebView for improved security and
reliability. Learn more
(https://developer.apple.com/documentation/uikit/uiwebview).
How do I go about doing that? Is there a build hint or something?
Additional Information:
My app is using some CN1 extensions:
SENSORS,
BLUETOOTHLE,
JSON (required for BLUETOOTHLE)
As the BLUETOOTHLE extension uses a Cordova plugin, and Cordova was using UIWebView, I think that is the likely source.
According to Cordova's issue tracker, the Cordova plugin doesn't use UIWebView in its latest. It is possible that the build server has an old version cached. Try explicitly setting the version to 6.1 by adding the following build hint:
ios.pods=Cordova ~> 6.1
You'll already have this build hint, you just need to add the "~> 6.1" part.
Please post to indicate whether this fixed your issue, and I'll update the cn1lib to automatically add the version to the build hint.
Codename One doesn't use UIWebView at all. Make sure all your cn1libs are up to date and list them. Review your own native code and dependencies if you have any to make sure there's no usage there.
I installed my application play store seamlessly. However, when I tried to install the App Store, the application was rejected and I received the following message.
Guideline 2.1 - Performance - App Completeness
We discovered one or more bugs in your app when reviewed on iPad running iOS 12.3.1 on Wi-Fi.
When we launched the app, app displayed a splash screen and no further action occurred in the app during the review.
Next Steps
To resolve this issue, please run your app on a device to identify any issues, then revise and resubmit your app for review.
If we misunderstood the intended behavior of your app, please reply to this message in Resolution Center to provide information on how these features were intended to work.
For new apps, uninstall all previous versions of your app from a device, then install and follow the steps to reproduce the issue. For updates, install the new version as an update to the previous version, then follow the steps to reproduce the issue.
Resources
For information about testing your app and preparing it for review, please see Technical Note TN2431: App Testing Guide.
For a networking overview, please review About Networking.
Please see attached screenshots for details.
When I write flutter doctor there is no problem.
I tried the application on the real device again no problem.
But the app store made such a turn. Does anyone know the reason or are having the same problem?
i faced same problem with android version of flutter app, when testers install app from google play, the white screen appear, but when test direct apk on device the app not installed appear.
That problem happen after i update android sdk tool to version 30
after long search, i solved the problem with step:
in dependences in android\build.gradle downgrade gradle from 4.0.0 to 3.5.0 as the default value new flutter app determined
in app\build.gradle downgrade compileSdkVersion to 29 and so targetSdkVersion to 29 too
run the flutter clean command
Resolved
https://www.flutterforum.org/d/97-white-screen-app-content-failed-to-load-after-launch-released-ios-app
Thank you!
It took me three days. But solved ...
Make sure you followed the developer guidelines carefully here at this link:
https://flutter.dev/docs/deployment/ios#create-a-build-archive
Steps to generate ipa:
Execute the following command flutter build ios --release
To ensure that Xcode refreshes the release mode configuration, close and re-open your Xcode workspace. For Xcode 8.3 and later, this step is not required. Finally Select Product > Archive to produce a build archive.
Hope this helps :)