Re: Huawei P40 Lite Google Play
Lora Ceasor
I have an app with the usual Google ad and in-app-payment stuff. It's accepted into the Play Store all right. Now I'd like to make it support both GMS and HMS at the same time (based on the availability of the appropriate services, the app can decide which platform to use). The app, with the Huawei functionality built in, works just fine while testing on my own devices.
However, as soon as Huawei's libraries are bundled with the app, the Play Store Console simply refuses it. No error message, just a red exclamation point. There's no doubt about the situation, I started to remove the Huawei-related parts one by one and as soon as the last bit was removed, the bundle was automagically accepted again.
Yes, sure, I might have made some error I'm not aware of but the situation is, well, rather suspicious. If it makes any difference, I use Flutter and I try to upload an app bundle, not APKs, as per normal these days. The HMS library that seems to make it or break it is com.huawei.hms:hwid:4.0.0.300 from the maven repo at
Any existing app that is currently using an alternative billing systemwill need to remove it to comply with this update. For those apps, weare offering an extended grace period until September 30, 2021 to makeany required changes. New apps submitted after January 20, 2021 willneed to be in compliance.
No matter what the policy says, the Play Console seems to enforce it already. And as I found by looking into the app bundle, the flavor approach is just not enough. Even with the other flavor, there will remain some packages referenced by Flutter. Maybe just the referenced names, not the actual code after tree shaking, but this is already enough for the refusal.
So, at the end of the day, I really think this question needs to be sorted out and some clear guidelines found for and by ourselves, developers, if we really want to write cross-ecosystem, single source Flutter apps. As for me, I sure want to do it.
Create two subpackages inside your project. They look like normal Flutter packages but reside inside your app. Basically, create two folders, gms_support and hms_support beside your usual lib. Both are packages with the usual structure:
Put all your vendor-dependent stuff into identically structured files inside the respective lib\src folders and make sure both XXX_support.dart files export them the usual way. The implementations should use the same classes and same signatures. Each pubspec.yaml refers to its own, vendor-specific Flutter plugins required for their implementation.
Different App store has different requirements for In-App Purchase Kit. The possible cause for the Play Store Console refusing your app is that your app integrated with other IAP Kit, and it does not meet the requirements of the app store review guide. You are advised to make your project support different app packages for different channels, to adapt different app store requirements.
If your app needs to support multiple build types or flavors, configure the agconnect-services.json configuration file downloaded from AppGallery Connect for your app to implement the function. The agconnect-services.json file provides configuration information required by various services in your AppGalleryConnect project. Therefore, if you need to use multiple flavors to release different app versions, copy the agconnect-services.json file to the folder of each flavor and configure it.
If your project needs to support different app packages for different channels, the package name needs to vary depending on the channel. Change the package name in productFlavor in the build.gradle file under the app directory.
The preceding sample code shows different packaging configurations for different channels, Huawei and Amazon. The package names are different for the two channels. If the same agconnect-services.json file is used for the two channels, the package name verification fails.To support multiple channels, you need to add the agconnect-services.json file to the flavor folder of only the Huawei channel and ensure that the AppGallery Connect plug-in version in the project is 1.2.1.301 or later classpath'com.huawei.agconnect:agcp:1.2.1.301'). If the plug-in version is earlier than 1.2.1.301, upgrade it to 1.2.1.301 or later.
Hello, I have the same issue.
I have HUAWEI MediaPad T3 and just bought spin bike Viking S100M. The bike works only with android bluetooth and not IOS but my tablet is only compatible with Zwift companion and not Zwift main app. either by web or google play
Hi, dears! I heared about Brave, that it plays youtube in the background on the mobile. I have a Huawei P20 Lite and that option only worked once and now it does not work anymore.
Steps to Reproduce:
I have tried just getting the Google Play Store, as well as Google Play Services from a APK downloader online, but it just shows "Install Core GMS Packages to use google play" This is my main problem.
Huawei phones like the Mate series or the P series (meant for America) can just download an APK for the GMS Installer. But on the Huawei Enjoy 7, it doesn't work. (same message when opening google play)
Here's where I find that it gets tricky, according to this forum post and this other stack exchange post, you need to use TWRP to install GMS. (the stack exchange one isn't exactly relevant to my situation because it is a Mate 9)
To anyone experienced with computers/android using TWRP or something that has full access to your phone can have damaging consequences if done wrong. The forum post has a small guide that can somewhat help but it isn't very clear. This other stack exchange post also shows how to use TWRP (there are also links to official guides) but it isn't exactly the same as what the forum post suggests me to do.
What I want is a very clear and detailed guide that has official information to back it up to show my how to properly install Google Play on a Huawei Enjoy 7 using TWRP. Or if there are any other methods on how to do so.
There is a thread in the XDA forums for your exact problem with the Huawei Enjoy The steps you need to follow are linked here.
This method requires you to unlock your bootloader, flash a custom recovery and install the OpenGapps package of your choice. For your convenience, I am copying all the steps here, but I would suggest you follow the instructions from their source.
(Bonus note: with help from Google Translate, you can get some more clarifications here)
Empires and Puzzles is not officially available in the Huawei App Gallery. Just like there are no Google services. Have you tried this? -to-install-google-play-store-on-any-huawei-smartphone-with-googlefier/
Nice, i enjoyed mine apart from the camera issues.
Some suggested it would be rectified via software update.
I had the iPhone 8 too which i loved. I prefer the full/edge to edge screen on the new phones.
I like the edge to edge display but in iPhone 8 size. When Apple released SE I was hoping it would be an edge display but disappointed.
I still prefer SE if I have to pay for the phone, why not save $600 right?
It is a shame what USA has done to Huawei, I bought two of their devices just before they were picked upon and very good quality, as good as Samsung but lower cost. So that has opened up market for Xiaomi.
Plug-and-play (PnP) is originally a term of computer hardware. In a PnP scenario, when a new external device is connected to a computer, the computer can automatically detect hardware resources without re-configuration or manual driver installation. PnP also refers to hot swapping, meaning that a hardware device, such as a USB device, can be directly connected to or removed from a powered-on computer.
In the data communications field, PnP in network solutions allows network devices and access terminals to automatically access the network upon network connection, saving manual configuration.
As network technologies develop fast and enterprise networks keep expanding, enterprises need to manage and maintain hundreds or even thousands of devices. In the early planning and deployment stages, work such as device installation, configuration, and upgrade takes up one third or even longer of the entire network management and O&M period. In addition, most of the work is simple and repetitive. Therefore, customers are in urgent need of simplified network device installation, deployment management, and software upgrade to further improve efficiency.
In addition, as the Internet of Things (IoT) continues to gain momentum and becomes ingrained in various sectors, more and more terminals of diversified types are connected to campus networks. Especially on large and midsize campus networks, access terminals include not only PCs and mobile phones, but also dumb terminals such as IP phones, printers, and IP cameras, leading to difficult terminal management. With a traditional network management system (NMS), an administrator can only view the IP addresses and MAC addresses of access terminals, but cannot perform refined terminal management. To plan and deploy different network services and policies for different types of terminals, the administrator needs to perform manual configuration. This results in complex service deployment and operations. As such, automatic identification and PnP of terminals become a must.
The next-generation PnP solution simplifies the network installation process. The SDN controller in the solution provides networks with automatic deployment capabilities, and seamlessly combines pre-deployment planning and subsequent network maintenance. This largely improves network management and O&M efficiency and reduces labor and time costs. The solution has the following advantages:
Take switches as an example. A cloud campus network with hierarchical tree structure has a large number of aggregation and access switches below the core layer. Implementing PnP on such switches greatly improves deployment efficiency and reduces deployment workload.
d3342ee215