In my app I'm using google maps. Now, I realized that you have a build google maps key and release google maps key. When I launch my signed apk into the app store for testing the google maps screen goes grey. And i have to keep signing a new apk and loading it into play store and then test it.
How do I test a release build? Please provide very simple and easy step by step instructions or if you know how to solve the problem with google maps that would be helpful.
Here is a screen shot of how i set up my google maps api in the console for my release one.
Test a release build
open Build Variants
set debug to release
Build and Run
For gray screen
Once you have got the release SHA set in dev console
This is main reason that I forget most of the time
You have two google_maps_api.xml files
One in this folder:
app/src/debug/res/values
Other in this folder:
app/src/release/res/values
But only the debug one contains your API key probably.
You can use gradle tasks to run a release build on emulator.
Default task name is installRelease
just start emulator and fire below command from terminal
./gradlew installRelease
this will install release build into emulator.
Related
My organization doesn't have Google Chrome natively installed within the Virtual Machines configured for automation CI and it's not allowed to install Chrome globally on those machines.
We are using protractor for automation of angular apps which goes really well with Google Chrome.
Is it possible to install Google Chrome at runtime for execution locally so that we can have smooth execution on those VM's. If yes what and how can i install chrome.
We are using TeamCity for CI/CD. Please help.
Update 29/12/2019: A suggestion, you containerize your app. Which means you need to include the step of chrome installation on when the image in being built on your VM.
Generally such a step is included in the Dockerfile.
more info on how to write Dockerfile: https://docs.docker.com/develop/develop-images/dockerfile_best-practices/
Within your angular app, to handle any browser's binary installation, I include it in package.json inside the scripts section:
"webdriver-update": "./node_modules/protractor/bin/webdriver-manager update --standalone --versions.standalone=3.8.0 --chrome --versions.chrome=76.0.3809.68",
This has worked for me in maintaining the dependency on the chrome versions.
I changed to new versions of Android SDK and NDK.
When I execute the command "cocos run -p android" in any cocos project directory, also a newly created one, then it compiles all sources correctly, but stops trying to build an apk, with the message:
Can't find right android-platform for project : "/Applications/MAMP/htdocs/42words/frameworks/runtime-src/proj.android". The android-platform should be equal/larger than 10
The Env-Variables are set to:
ANDROID_SDK_ROOT=/Applications/adt-bundle-mac-x86_64-20140702
NDK_ROOT=/Applications/android-ndk-r10
ANT_ROOT=/usr/local/Cellar/ant/1.9.3/bin
And they are correct. At
/Applications/adt-bundle-mac-x86_64-20140702/sdk/platforms
there is a android-20 folder. If I call cocos with
cocos run -p android --ap 20
Then the message is
The directory "android-20" can't be found in android SDK
What am I missing?
I had the same problem when I replaced my old copy of the Android SDK with the one from the Cocos Store.
Can't find right android-platform for project : "/Users/CurrentUser/ProjectName/frameworks/runtime-src/proj.android". The android-platform should be equal/larger than 16
Easy fix! Run android found at /android-sdk/tools/android and make sure that the Android version (in this case API 16) is downloaded.
here is my android_sdk_root, you lose /sdk?
export ANDROID_SDK_ROOT=/Project/adt-bundle-mac-x86_64-20131030/sdk
if not this reason, you can find this log in tools/cocos-console/plugins/project_compile/build_android.py
def check_android_platform(self, sdk_root, android_platform, proj_path, auto_select):
if you use python ,it's easy to find the reason by log
To me, the problem can be solve by installing the older version of android sdk. Open your android ndk folder and check for the newest version of the NDK. If it is android-21 for example, then you open AndroidSDK Manager, and install AndroidSDK Build tools 21. After that, try again to run your project.
In addition, depend on your target device, you may also want to install an equivalent Android SDK platform.
I have now followed all the Blackberry documention found here and here. Yet some how I keep getting the following error:
[BUILD] Populating application source
[BUILD] Parsing config.xml
[BUILD] Generating output files
[WARN] Failed to find debug token. If you have an existing debug token, please copy it to %HOME%/.cordova/blackberry10debugtoken.bar. To generate a new debug token, execute the 'run' command.
[WARN] Failed to find debug token. If you have an existing debug token, please copy it to %HOME%/.cordova/blackberry10debugtoken.bar. To generate a new debug token, execute the 'run' command.
I have created the bar using this link here (which wasn't even specified in the links above) Please can anyone explain this or point to a tutorial the gets one up and running to a hello world app for blackberry WebWorks as the Blackberry links really don't help
I've not been able to find useful instructions either, however I have the native SDK installed alongside the Momentics IDE and it has a wizard that created all the necessary for me:
Create a new BB10 project
Right click on the project root node in the Project Explorer
Open BlackBerry Tools and then Configure Targets
A wizard will start allowing you to create the CSK and BAR files, and also deploy them to your devices if there is no CSK in C:\USERS[User]\AppData\Local\Research In Motion
If the CSK already exists in the path above you'll be able to create and install Debug Tokens with your existing CSK.
After you've created the token I had to copy it to C:\Users[User].cordova and rename it to blackberry10debugtoken.bar to get the build in the WebWorks UI to work.
However, though I've now got an installed DebugToken on my simulator, and the Webworks UI happily builds the project, the Build and Install action fails with an error message as follows:
fs.js:418
binding.open(pathModule._makeLong(path),
^
TypeError: path must be a string
at Object.fs.open (fs.js:418:11)
at Object.fs.readFile (fs.js:206:6)
at _self.findConnectedSimulator (D:\WebWorks\HelloWorld\platforms\blackberry10\cordova\lib\target-utils.js:190:12)
at Object.async.series.ip (D:\WebWorks\HelloWorld\platforms\blackberry10\cordova\lib\run-utils.js:48:17)
at D:\WebWorks\HelloWorld\platforms\blackberry10\cordova\node_modules\async\lib\async.js:561:25
at iterate (D:\WebWorks\HelloWorld\platforms\blackberry10\cordova\node_modules\async\lib\async.js:131:13)
at Object.async.eachSeries (D:\WebWorks\HelloWorld\platforms\blackberry10\cordova\node_modules\async\lib\async.js:147:9)
at Object.async.series (D:\WebWorks\HelloWorld\platforms\blackberry10\cordova\node_modules\async\lib\async.js:560:19)
at Object.getTargetName (D:\WebWorks\HelloWorld\platforms\blackberry10\cordova\lib\run-utils.js:45:15)
at fn (D:\WebWorks\HelloWorld\platforms\blackberry10\cordova\node_modules\async\lib\async.js:579:34)
I'd be grateful for anyone who is able to further my discovery and make the WebWorks UI work without having to install Momentics & the native SDK, or to get the deployment to the simulator working...
The current SharpCompress.WindowsStore.dll library published on Nuget is build in Debug mode. I got this error from the Windows Store App Certification Kit.
Error Found: The debug configuration test detected the following errors:
The binary SharpCompress.WindowsStore.dll is built in debug mode.
Is there any way to have/compile the SharpCompress lib in Release Mode?
I'd rebuild it in release mode.
What, you didn't think about that?
It's on NuGet, right? NuGet packages often list a project site. So looking at the page I can see the link points right over here. That's on GitHub. That's where source lives.
You can either fork it (which there isn't really a point, since you don't want to develop it), clone it (aka use a Git tool such as GitHub for Windows) to your local machine, or just download the latest code in a zip file.
From there you can build in release mode and away you go. May not be just that easy, as there might be some dependencies or such that need resolving. Now off you go.
I go http://developers.box.com/onecloud/ to download the Android SDK. I got box-box-android-sdk-5482811 Is this the latest version?
Because when I open up the OneCloudAppToAppSample, even the R. variable is not well defined. And I cannot run the sample code.
Where can I find more help or documentation on using Box with Android SDK?
The SDK is being improved quite frequently, so our advice would be to always use the latest version on the "master" branch. We consider the master branch to be our stable release. In your case, 5482811 should work fine.
Regarding your issues with the sample app, I don't seem to have any problems compiling it off of a fresh download. I can think of one thing you might be running into:
The sample app was configured to point to target "Google APIs:15". It's possible you don't have this installed (through the Android SDK manager). We actually should not have configured this build target, since the project doesn't use the Google APIs, and we'll fix that in our next release.
In the meantime, could you try this (assuming you're using Eclipse):
Right-click on the OneCloudAppToAppSample project and go to Properties.
Go to the Android section on the left, and change the build target to Android 4.0.3 - 15 (not the Google APIs version).
Project -> Clean -> Clean all projects.