Missing 64-bit support / Missing Push Notification Entitlement Phone - android

I am trying to submit my app and I keep getting this issue. I have updated the Phonegap and cordova but still get his issue. I have also regenerated the app using command line after the update but no luck.
Email below.
Dear developer,
We have discovered one or more issues with your recent delivery for .
Your delivery was successful, but you may wish to correct the
following issues in your next delivery:
Missing Push Notification Entitlement - Your app appears to include
API used to register with the Apple Push Notification service, but the
app signature's entitlements do not include the "aps-environment"
entitlement. If your app uses the Apple Push Notification service,
make sure your App ID is enabled for Push Notification in the
Provisioning Portal, and resubmit after signing your app with a
Distribution provisioning profile that includes the "aps-environment"
entitlement. See "Provisioning and Development" in the Local and Push
Notification Programming Guide for more information. If your app does
not use the Apple Push Notification service, no action is required.
You may remove the API from future submissions to stop this warning.
If you use a third-party framework, you may need to contact the
developer for information on removing the API.
Missing 64-bit support - Beginning on February 1, 2015 new iOS apps
submitted to the App Store must include 64-bit support and be built
with the iOS 8 SDK. Beginning June 1, 2015 app updates will also need
to follow the same requirements. To enable 64-bit in your project, we
recommend using the default Xcode build setting of “Standard
architectures” to build a single binary with both 32-bit and 64-bit
code.
After you’ve corrected the issues, you can use Xcode or Application
Loader to upload a new binary to iTunes Connect.
Regards,
The App Store team

Goto developer site & enable push notification In your ptovisioning profile for production , recompile with latest provisioning profile & resubmit it.
Regarding 64 bit support have you changd active architecture setting from build setting it should be standard atchitecture.

Found out that this is just a warning message. The App got accepted!
Missing Push Notification Entitlement - Did not matter as I did not use the notification functionality.
Missing 64-bit support - You have to have the latest version of phonegap
Thanks for your help guys

Related

How to remove Facebook tracking from default React Expo project?

I created a very basic React Expo application and compiled it to an Android APK. In the Google Play Store I stated that my application does not collect any user data. To be save I installed the APK on my Android device and searched for trackers with TrackerControl. I was shocked to see that the App is sending data to Amazon and Facebook, although I am 100% sure that I did not implement this!
Is there a way to get rid of this dammit sniffing? I can't put in all the effort to reimplement everything in another framework...
Update:
Let me give a reproducible tutorial. First I created a simple expo navite application in Ubuntu 20.04 LTS with
expo init my-app
cd my-app
Then I build the APK with
expo build:android -t apk
This will print a web link to the console from where I can download the APK after about one hour. I Download it directly with my Android Phone and install it. Then I check which Tracker control and it recognized a lot of tracker software!
Translated to English: "Recognized tracker libraries:
Amplitude
Facebook Ads
Facebook Analytics
Facebook Login
Facebook Share
Google AdMob
Google Analytics
Google Firebase Analytics
Google Firebase Analytics
Google Play Install Referrer
Segment
"
And it immediately starts sending data to Amazon.com and Facebook.com:
It shows writes that sending data to Amazon.com is necessary (which it is not!) and the social tracker for Facebook which I also never installed! How can I remove all these trackers and at what point are they added? Maybe during the build process? Because it builds on some server where I lose control about the build process.
To get rid of these libs, you could switch to EAS Build (free tier with some limits like 30 lower prio builds/month, ...). We regarded this rather acceptable and I can confirm, that there are no trackers left using that approach:

Dependent app configuration Wear Os, gradle vs manifest for distribution

Dependent app configuration Wear Os, gradle vs manifest for distribution
Hello, I need help, this is the first time that I see apps for Wear Os by Google, in this case I made an app dependent on the one on the phone.
Add the settings from the phone and wear app but when you go to "Advanced Settings" -> "Version types" -> Add "Wear Os by Google" and accept the Wear policies, it will be revised and rejected.
The only message I get by mail is the following
Publishing status: Rejected
Your app has not been accepted into Wear OS. This does not affect your app’s status on Google Play.
Eligibility Issue
Does not mention Wear OS
Your app does not mention Wear OS in the store listing. Please refer to the Wear OS by Google app quality guidelines for more information.
So it seems to me that you need some particular configurations either in the manifest or in gradle that I am ignoring, it should be noted that I have been guided by the official documentation but I have not had a satisfactory result.
Thanks in advance!

Google Play Security Issues?

This is my first time submitting an app to the Google Play store, so I'm not very experienced with the process at all. After struggling for a bit to get it to build correctly, I was finally able to upload an app bundle and send it in for review. A few minutes later I got an email saying my app was "vulnerable to Intent Redirection" and recommended the following article for support: https://support.google.com/faqs/answer/9267555. The problem is I don't understand much of what the article is saying! As far as I know, I haven't messed with anything like this. I've only downloaded the base NDK and SDK stuff from Unity Hub, and I haven't changed any of the code in Android Studio at all. I asked Google for support, and they said:
"We’ve identified that your app is using the AliPay SDK or library, which facilitates the transmission of phone number information without meeting the prominent disclosure guidelines. If necessary, you can consult your SDK provider(s) for further information or please upgrade AliPay SDK version to 15.5.5 or higher."
Please help! Is there an easy fix to this that I'm missing somehow? I don't even know what AliPay is, as I said I'm a total beginner here. In case it's useful info to have, I'm using Unity 2019.2.13f1 on a Macbook Pro running High Sierra 10.13.6.
Well, do what the message says "upgrade AliPay SDK version to 15.5.5 or higher".
Just go to Android Studio and open your build.gradle file then update that lib version. It will be marked with a yellow line, that means that lib has an update. Focus on that line, then do Alt + Click then Enter, now sync and you've done. Upload the new apk.

How do I add Firebase Cloud Messaging to Xamarin.Forms app?

Google has replaced GCM (Google Cloud Messaging) with the new FCM (Firebase Cloud Messaging) for push notifications. I am trying to implement push notifications in my Android (Xamarin.Forms) project. It appears that FCM is not yet supported for Forms due to Google Play Services dependency issues (see details below). When I attempt to implement using the old GCM system, the Google Developer Console will not allow me access the GCM API credentials page (just redirects me to FCM). Does anyone have any suggestions to get push notifications working with Android in a Xamarin.Forms solution?
Note: I am using Azure Notification Hub to send the messages (I have iOS already working)
Dependency Issue: The latest Xamarin.Forms package is dependent on Xamarin.Android.Support.v4 (23.3.0). Xamarin.Firebase.Messaging is dependent on Xamarin.GooglePlayServices.Basement (32.961.0). Xamarin.GooglePlayServices.Basement (32.961.0) is dependent on Xamarin.Android.Support.v4 (>=24.2.1).
My android solution is on:
https://forums.xamarin.com/discussion/70248/firebase-configuration
Just search for my name as UmutBebek. I'm using pushSharp to send push-notifications from my own server. There is a simple example for that too.
Almost a year later and this should not be an issue anymore.
I have a Xamarin Forms (2.4.0) app pegging Xamarin.Android.Support v4 at version 25.1.0 and I just installed Xamarin.Firebase.Messaging (42.1021.1) happily alongside it via nuget.

Appgyver Steroids and Android push notifications even possible?

Been trying to get Steroids working with push notifications on Android and keep hitting a brick wall.
As far as I can see, there's no official support for https://github.com/AppGyver/PushPlugin, and the Urban Airship addon is currently iOS only.
When I set the custom plugin in the build configuration, I get some pretty nasty build errors. This is with just a freshly created and deployed steroids project, and just generally can't even get to the point where I have a build to play around with push notifications :(
There was some rumbling about the devs prioritising pushplugin around Dec 2013, but unsure if that ever actually materialised?
So I have:
steroids create pushTest
steroids deploy
...then I goto https://cloud.appgyver.com/applications/, configure my app in the android tab by adding this to the custom plugins...
[
{"source":"https://github.com/AppGyver/PushPlugin.git"}
]
Then run a build on 4.0.2. I am trying a scanner build, tried ARM, x86, and both, and keep coming back with build issues as above, or on some of the other forks ones that are a bit more vague, but I suspect those forks to be old.
So my question: Is it even possible to get push notifications working with Steroids under Android?
There's now an officially supported fork of the Push Plugin which works with the AppGyver Android Client: https://github.com/AppGyver/PushNotifications
The minimum required version for the Android client is 4.0.4-edge3.
Please see the Push Notification guide for instructions how to create the required iOS Certificates and the Google GCM API key.

Categories

Resources