I have created an ionic 4 project that makes use of the google maps APIand their development tools. I would like to build the peoject now for android release i ran the command
ionic cordova build --release android
But then i get the following error message
* What went wrong:
Execution failed for task ':app:processReleaseGoogleServices'.
> File google-services.json is missing. The Google Services Plugin cannot function without it.
Searched Location:
I have downloaded the google-services.Json from firebase but I am unsure where i should place it and what files i need to edit. If you want the ciontents of a certain file let me know and ill put it here. Thank you for any help
Try copying this file into: \platforms\android
There is a known issue when this file on certain versions of Android Studio gets corrupted etc. So just double check that the file is always there if you see this again.
If you are on never version of Android studio:
google-services.json needs to be in app/google-services.json. Then your config.xml needs to have:
<resource-file src="google-services.json" target="app/google-services.json" />
Related
I write basic web apps for my personal use and am only one step above a noob. The current version of my web app runs a different code.gs file than the one that is saved, i.e., the code.gs file that comes up when I open the project from the apps script dashboard. I can't find the currently running file in the previous deployed versions in the Manage Deployments dialog. It seems to me that a version is running that is kind of inbetween deployments. Is there a way to display and edit the file that is currently in use by the web app? Thank you.
To run the latest code you can create a new version.
On the new IDE you can't see the previous version code, on the old IDE if you go to File -> See version history.
But to run the script you have on the screen on the new IDE, you have to deploy a new version.
Can you help me get my crashes symbolicated?
In Xcode 7.3, Window -> Organizer -> Crashes, I have crash reports from my latest TestFlight builds. They were built on this Mac, and all the archives with the corresponding dSYMs are in the Archives tab. The app is divided into a number of frameworks and the main app, and many are a mix of Swift and Objective C. In the crash log I can see the name of the frameworks and app listed correctly, but all the entries for my frameworks and app are in hex. UIKit is symbolicated just fine.
When I look in iTunes Connect, it says "Yes" to "Includes Symbols" and allows me to download the dSYMs. When building, the "Debug Information Format" option was set to "DWARF with dSYM". I tried setting "Strip Debug Symbols During Copy"
and "Strip Linked Product" to "No" to see if that made a difference. It didn't.
I cannot find the symbolicatecrash app on my system, not even in /usr/bin or /Applications/Xcode.app/Contents/SharedFrameworks/DTDeviceKitBase.framework/Versions/A/Resources/symbolicatecrash, but I have an older Xcode 5 where I could grab it. However, it does not resolve the symbols anymore.
I have the same problem in Instruments, if I profile my app, UIKit is symbolicated just fine, but my frameworks and app only show hex.
I know there have been a lot of posts about this, but I have going through them a lot from the 7.3 beta period and until now and have not found a solution
The location of symbolicatecrash has changed in Xcode 7.3:
/Applications/Xcode.app/Contents/SharedFrameworks/DVTFoundation.framework/Versions/A/Resources/symbolicatecrash
After reading this:
https://developer.apple.com/library/content/technotes/tn2151/_index.html
you find out that the App Store is responsible for symbolicating crash reports that come from TestFlight – not Xcode. And it appears the App Store is very unreliable at doing it.
Here's a workaround.
Go to the Archives tab in the "Organizer" window and make sure that for whatever build you need to symbolicate a crash report for, you have clicked the "Download dSYMS..." button over on the right side of the page. This is required if you are uploading in BitCode.
Attach an iOS device so that it appears in the "Devices" window.
Select the device and click "View Device Logs".
Now, go back to the Organizer Window, select the "Crashes" tab and select one of the crashes that did not get symbolicated.
Right-click on it and select "Show in Finder".
Right-click on the revealed .xccrashpoint bundle and select "Show Package Contents".
Drill down into DistributionInfos -> all -> Logs.
Drag any of the .crash files into the left side of the "View Device Logs" pane open in the Devices window.
Wait a second or two for Xcode to symbolicate the crash.
Same here. Having a hard time finding the symbolicatecrash after upgrading to 7.3.
However, you can still use the atos though.
You can find the tutorial here Symbolicate crash in iOS8 with Xcode 6 .1
I do not upload symbols with my application, so the App Store cannot symbolicate for me. I used the following workaround to symbolicate all of the crashlogs that XCode downloads from the store. These instructions are for XCode 8. The paths for the symbolicate crash app will vary from version to version of XCode but the ideas should be the same in each version.
Place your symbols where the symbolicator can find them: Place your symbols (.dsym) file in your Archives directory. You can find this by going to Organizer, context clicking on an archive and choosing "show in finder". Navigate up to the Archives directory (e.g. /Users/USERNAME/Library/Developer/Xcode/Archives) and place your dsym file there. It can be in other locations as well, it's just that I've verified that this one works.
Download the crash logs: In XCode, make sure that you've downloaded the crashlogs for the build you want to symbolicate (Organizer->Crashes, click on your app and then choose the version of your app in the panel to the right of the list of apps).
Locate the crash logs on disk: In the panel that has the App Version and build number, context click on one of the crashes and choose "Show in Finder". Navigate up to the "Crashes Folder" and note this location e.g.: /Users/USERNAME/Library/Developer/Xcode/Products/com.company-name.Your-App/VERSION/Crashes
Setup DEVELOPER_DIR for symbolicatecrash on the command line: Open a terminal window and CD to the crashes directory from step 3 and set the DEVELOPER_DIR like this: cd /Users/USERNAME/Library/Developer/Xcode/Products/com.companyname.Your-App/VERSION/Crashes/
export set DEVELOPER_DIR=/Applications/Xcode.app/Contents/Developer
(this should be the location of the "Developer" directory inside of your XCode app bundle).
Locate the symbolicatecrash script: symbolicatecrash knows how to find your symbolicate crash logs using the dsym from step 1. Apple moves it around from version to version of xcode. You can find it like this: find /Applications/Xcode.app/ -name symbolicatecrash. In XCode 8, it is in /Applications/Xcode.app/Contents/SharedFrameworks/DVTFoundation.framework/Versions/A/Resources/symbolicatecrash
Backup your crashes folder You may want to backup your crashes folder (/Users/USERNAME/Library/Developer/Xcode/Products/com.companyname.Your-App/VERSION/Crashes/)
Symbolicate all of your crashes: Be sure that you are still in the Crashes directory from step 4 and type
for i in `find . -type f -name \*.crash`; do cat $i | /Applications/Xcode.app/Contents/SharedFrameworks/DVTFoundation.framework/Versions/A/Resources/symbolicatecrash --output $i.sym; mv $i.sym $i; done;
This symbolicates each .crash file into an output file and then copies that back over the original, unsymbolicated file.
View Crashes Return to the crashes organizer and view the symbolicated crashes
I tried to copy symbolicatecrash file from xCode 7.2 and pasted it in xCode 7.3 in the following path:
/Applications/Xcode.app/Contents/SharedFrameworks/DTDeviceKitBase.framework/Versions/Current/Resources/
Am using Crasher script to symbolicate the crash reports How to use Crasher
According to the documentation of Xcode 9.0:
The Crashes Organizer symbolicates unsymbolicated logs, if they are
selected, using a local .dSYM indexed by Spotlight. (22550064)
You can check out more on this in Xcode's Documentation.
I want to launch my Libgdx project on HTML 5 platform but there is Error like
The type com.google.gwt.core.client.EntryPoint cannot be resolved. It is indirectly referenced from required .class files GwtLauncher.java /Digestive-System-html/src/com/me/mygdxgame/client
The project was not built since its build path is incomplete. Cannot find the class file for com.google.gwt.core.client.EntryPoint. Fix the build path then try building this project Digestive-System-html
I googled but unable to resolve this problem. Any help wiil appreciated
thanks...
Hello vishal to my knowledge if you go through this you can setup libgdx project on HTML 5 based browser platform.As of version 0.9.3, libgdx comes with an easy to use application called "Libgdx Setup".The following steps will create everything needed to develop for the desktop, android, html 5.
Download the gdx-setup-ui.jar from http://libgdx.badlogicgames.com/nightlies/dist/gdx-setup-ui.jar. The jar is also contained in all stable and nightly releases.
Execute the jar by double clicking it or from the command line via java -jar gdx-setup-ui.jar
Specify your project's configuration (Configuration Panel).Specify the libgdx stable/nightly release zip file or press one of the buttons to download the latest stable/nightly release (Library Selection Panel).
Hit the "Generate projects" button (Generation Panel)
Open Eclipse and import the generated projects into your workspace.
File -> Import -> Existing Projects into Workspace
Click "Browse", select the folder containing the generated projects.
Make sure all the projects are checked, then click "Finish"
To fix the error of the HTML5 platform, go to the "Problems" view, right click the error message "The GWT SDK JAR gwt-servlet.jar is missing in the WEB-INF/lib directory" and select "Quick Fix".
Click "Finish".
I was trying to submit my second app update and it failed submission after passing validation. This is the error:
"Unable to create configuration directory:/Application/Xcode.app/Contents/iTMSTransportation.woa/.itmstransporter. Cannot save local copy of remote diagnostic configuration;local path is not writable".
My screen shot of the error cannot be attached. I know it is not a network error at Apple's end because it specified a path in the Application Loader in Xcode. Since the system has read and write permissions here, it cannot be because I changed something. I submitted another app successfully earlier on the same day without a problem (as usual). I am at my wits’ end. Anyone experienced this?
Since there is no “Build for Archiving” in Xcode 5 (like in Xcode), I started with following steps:
1 - From the Xcode Product menu I selected “Archive” item
2 - After the Build, the organizer window appeared in the foreground with my archive in it.
3 - I clicked the “Validate…” button and it executed that successfully.
4 - When I clicked the “Distribute…” button, it started uploading the app but failed and came back with the aforementioned error. I went to the folder to see if any folder in the directory path is locked and also to see who has read and write permissions. It is not me but the system. I did a Disk Permission Repair in Disk Utility but that didn't help.
I then removed the offending file “.itmstransporter.” and tried to submit but got a different error. I put it back and took out the other two (ITMSTransporter.cmd and WOBootstrap.jar” but produced a different error. So I restored the folder to its original contents and returned to where I started - stymied. I have considered installing a new version of Xcode 5.0 but I don't know if that will help.
My OS:Mountain Lion 10.8.5, Xcode 5.0, MacBook Retina (first retina in 2012). Project compiled for iOS 7 in the Build Settings.
Thanks for any pointers.

I had the same issue. I copied the whole "Application Loader" out of the XCode package to somewhere else and after that, uploading from the Application Loader worked fine.
I have a jenkins job using xcode to build my ipa file. That is all working great. Right now I just have the Marketing version set to ${BUILD_ID} and the technical version set to ${BUILD_NUMBER}. I also have Release configuration specified and my job is set to archive the ipa files as a post build action. I believe those combination of settings causes my resulting IPA file to be the following:
Target-Configuration-BUILD_NUMBER.ipa
So if my target was named BillyBob and this was the 23rd successful build, my resulting .ipa file is:BillyBob-Release-23.ipa
I want to setup a job or post-build action to upload my file to testflight on a successful build.
I can not figure out what to set the file parameter of the testflight API to so that it will always find the latest build file, I don't think there is a wildcard available or if there is I don't know how to set it.
Originally, when I wasn't setting the technical version as part of the build I had it just pointed to the -1.0.ipa version of the file it was creating and that would get uploaded fine.
I've tried using both the testflight plugin for jenkins and just a curl shell script command.
I will also point out that I'm not an iOS developer, I've just been trying to help the project by setting up the automated build, so my guess as to how that file is getting generated could be way off.
***UPDATE
So it looks like this current open issue is kind of what I am looking for
jenkins issue section
For now, I just had my job specify an output path that is the workspace of my upload to testflight job.
It looks like in the Testflight app, if you don't specify anything for the IPA file, it looks for one in the workspace directory of that job. So I could probably also put in a request to the testflight plugin to allow you to specify a path in the IPA setting and have it find the .ipa file in that path, that currently does not work.
If I was better at scripting I could probably also handle it in a shell command using the curl command to upload to testflight.
Leaving those fields empty in Jenkins fixed it for me.
If you do not specify the ipa/dsym file(s) they are searched for
automatically in the workspace.
As you can see from:
https://wiki.jenkins-ci.org/display/JENKINS/Testflight+Plugin
Version 1.3.1 (Jan 12 2012)
* Default IPA upload