What should I do if the tool package fails to run when I integrate the HUAWEI AppGallery Connect SDK to Eclipse? - huawei-mobile-services

I had recently planned on integrating the Crash SDK to my app. However, my app was developed through Eclipse and the integration process was different from that in Android Studio.
By referring to the official materials, I downloaded the tool package and used it to generate an Eclipse project package.
However, when the build.bat file in the aar2eclipse/aar directory was executed according to the procedures in the document, an error was reported in the command line. The error information was as follows:
FAILURE: Build failed with an exception.
What went wrong:
Task ' assembleRelease ' not found in root project ' aar '.
[![enter image description here][1]][1]

I first thought that the problem might be caused by my company's intranet. But when I connected to the Internet, the problem remained unsolved.
Then I guessed that it might have something to do with the Android development environment.
I borrowed a colleague's PC to execute the build.bat file, and it that did the trick. Therefore, I was able to conclude that the problem was caused by incorrect configurations in the Android development environment. I compared the configurations on the two PCs and found that the environment variables were different. ANDROID_HOME was missing from the environment variables on my PC.
Cause
Huawei's Eclipse tool package is unable to run properly and reports an error without the ANDROID_HOME variable.
Solution: Right-click This PC and choose Properties from the shortcut menu. In the displayed dialog box, click the Advanced System Settings tab and then click Environment Variables. In the System Variables dialog box, create a new ANDROID_HOME parameter.
Set the value to the installation path of the local Android SDK, and the problem will be resolved, as shown below.
Reference:
https://developer.huawei.com/consumer/en/doc/development/AppGallery-connect-Guides/agc-get-started#h2-1587519820720

Related

Where can I find full prerequisites list for releasing flutter windows desktop app?

I'm absolute newb to flutter, with objective to focus more on windows-desktop apps. It seems that flutter running on windows-desktop require way more DLLs than mentioned on https://docs.flutter.dev/development/platform-integration/windows/building page. I have created and build absolute minimum Flutter application on my dev machine (Win10 22H2). All went fine, starts and runs as expected.
I have then put mentioned DLL in the folder, along the runner app (testapp.exe) and copied over to test machine running Windows Server 2019 Version 1809 as VMWare image. Both Debug and Release versions of Flutter app (testapp.exe) fails. Debug version fails with MessageBox shown "Code execution cannot proceed because MSVCP140D.dll was not found" which I assume is a debug version of msvcp140.dll (this was present in the testapp.exe location while running).
Trying to run Release version produce no error message at all, application is visible in TaskManager for brief second and exits. Running ProcMon against test application shows it seeks numerous other DLLs which were not mentioned in the flutter docs (see attached pic for reference)
Question - is there some more comprehensive list of Flutter windows-build requirements ?

How to fix a packaged WinUI3 app build, what makes trouble with ProcessorArchitecture?

Today i'm trying to build a .NET 6 WinUI3 App in AzureDevOps. My csproj contains:
<TargetFramework>net6.0-windows10.0.22000.0</TargetFramework>
<TargetPlatformMinVersion>10.0.17763.0</TargetPlatformMinVersion>
<RootNamespace>MyApp</RootNamespace>
<ApplicationManifest>app.manifest</ApplicationManifest>
<Platforms>x86;x64;arm64</Platforms>
<RuntimeIdentifiers>win10-x86;win10-x64;win10-arm64</RuntimeIdentifiers>
<PublishProfile>Properties\PublishProfiles\win10-$(Platform).pubxml</PublishProfile>
<UseWinUI>true</UseWinUI>
<EnableMsixTooling>true</EnableMsixTooling>
<ApplicationIcon>Assets\2764a994e49c43a2932b6d7f465e99eb.ico</ApplicationIcon>
<PlatformTarget>x64</PlatformTarget>
As "Build Platform" i have defined in Pipelines variable "x64". As error i become:
[error]C:\Users\VssAdministrator.nuget\packages\microsoft.windowsappsdk\1.1.2\buildTransitive\Microsoft.Build.Msix.Packaging.targets(1016,5): Error : Packaged .NET applications with an app host exe cannot be ProcessorArchitecture neutral. Please specify a RuntimeIdentifier or a Platform other than AnyCPU.
I'm wondering why this happens and how to fix it?
I figured this out! In Visual Studio, right click on your solution and click properties. For me, a few of the projects didn't have a Platform selected. I changed them all to x64 and the build succeeded. Hope this helps.

JDK, SDK, and Gradle errors trying to build a Unity game for Android

The question:
My environmental variable JAVA_HOME is set to the location of my manual installation of Java, so why is Unity claiming it is an invalid directory?
Supporting information:
I'm using Unity to build a game for Android phones with the intent on putting it on the Google Play Store for a client. We need to use a Google Ad plugin for managing ads in the game. However, when I put the plugin into the project I can no longer build the game.
When going to Assets > External Dependency Manager > Android Resolver > Resolve, it claims it succeeds.
But when I try Assets > External Dependency Manager > Android Resolver > Force Resolve or even building the project I get a failure and a perplexing error.
Originally I had the same problem as: Intellij Gradle terminal ERROR: JAVA_HOME is not set
When I tried the solutions there as well as following the steps at: https://javatutorial.net/set-java-home-windows-10
I've tried setting the environment variable both to the independent java installation as well as the location of Unity's JDK module and got an error that they were both invalid directories:
When I try to build I get the same error plus some additional errors:
I am unsure if the SDK error is related or not.
I already tried toggling these off and on, and even changing the installation targets to manual installations:
Possibly relevant information:
Using Unity 2019.3.0f6
InMobi Google Ads Unity Mediation Plugin Version 3.0.0
Windows 10 Pro
Java JDK 14.0.1
If Unity can't find JAVA_HOME it won't do anything, have you tried checking if you have that Environment Variable set correctly?
Check this thing.
Maybe you will need a Restart on you computer to see the changes.

I'm not getting an .exe for my game after building?

I am new to Unity3D and have been building a zombie survival game for my university course. My issue is after building my game I am not given a .exe file.
Some of the things I have already tried:
Reinstalling Unity
Spoke to my tutor who said I had missed out on some components needed when installing Unity - UWP Build Support (.NET) & UWP Build Support (IL2CPP). Reinstalled Unity with these components, still no .exe file.
Posted this question on the Unity Community - still waiting for an answer.
Try to reinstall unity with a different version or to change machine probably there are problems with your set up
Try to build without checking the Create Visual Studio Solution checkbox
File > Build Settings… is the menu item to access the Build Settings window
It’s simply a matter of choosing the build target in the build settings dialog, and hitting the ‘Build’ button. When building standalone players, the resulting files will vary depending on the build target. For the Windows build target, an executable file (.exe) will be built, along with a Data folder which contains all the resources for your application. For the Mac build target, an app bundle will be built which contains the file needed to run the application as well as the resources.
(you may have to complete your options in player settings or probably you missed to select platform)

Unable to automate Hybrid Android mobile app using appium

I want to automate test a basic Hybrid Mobile Application running in Android.I am able to launch the app in emulator but not able to enter the text in the login screen.
Getting error as
"Exception in thread "main"
io.appium.java_client.NoSuchContextException: An unknown server-side
error occurred while processing the command. Original error: No
Chromedriver found that can automate Chrome '53.0.2785'. See
https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/web/chromedriver.md
for more details. "
Please help me resolving this!!!!!
If you see chromedriver.exe change log you will get the version you require for hybrid app automation. The browser used in your device have versin 53+
See this url http://chromedriver.chromium.org/downloads [check ChromeDriver 2.24 details] it says it supports browser with version 53+. Get this exe from https://chromedriver.storage.googleapis.com/index.html?path=2.24/
How to connect with Appium -
If you are using appium desktop, it gets installed as windows application in program files folder. Now location of chromedriver.exe it uses is as mentioned below.
C:\Program Files (x86)\Appium\resources\app\node_modules\appium\node_modules\appium-chromedriver\chromedriver\win\chromedriver.exe [This location may be bit different in your case]
Replace above location chromedriver from downloaded chromedriver.exe(from step2)
Note - Ideally automation should work without throwing exception. Incase still it doesn't work then try 1+ or 1- version of 2.24
You got everything you need in exception message:
Go here https://github.com/appium/appium/blob/master/docs/en/writing-running-appium/web/chromedriver.md
and read explanation on compatibility.
No Chromedriver found that can automate Chrome '53.0.2785'
Appium was not able to get chromedriver for your emulator that have Chrome 53.0.2785
So the first solution is to get Chromedriver v2.26 and add absolute path to binary as chromedriverExecutable capability:
1) download chromedriver_win32.zip from the link above and unzip
2) in your code add capability with the path to chromedriver.exe:
DesiredCapabilities caps = new DesiredCapabilities();
...
caps.setCapability("chromedriverExecutable", "/abs/path/to/chromedriver.exe")
If you get new emulator, first check what browser version is preinstalled and try to upgrade.