I have added following code inside proguard-rules.pro for producing redable crash report once proguard enabled in my project.
-keepattributes SourceFile,LineNumberTable # Keep file names and line numbers.
-keep public class * extends java.lang.Exception # Optional: Keep custom exceptions.
I haven't add mappingsFileUploadEnabled in build.gradle. So that means as per crashlytics documentation, plugin will automatically upload mapping file.
When i build the project my mapping file generated under build->outputs->mapping
Anyone please tell me crashlytics plugin on which location uploading this mapping file automatically ? Can i view this file on crashlytics portal once plugin uploaded to mapping file ?
At the moment is not possible to see the uploaded mapping files in the Crashlytics dashboard.
After building the app, you would need to cause a test crash and see if the code has been deobfuscated. If it is, then that means the mapping file got uploaded correctly.
If it doesn't, you could try running the gradle task that upload the mapping file and see if there are errors. for this you can use this command:
./gradlew app:uploadCrashlyticSymbolFileDebug --console=plain --debug | grep "com.google.firebase.crashlytics"
Related
I make a flutter project in the android studio and as soon as I looked into the androidmanifest.xml file it showed error MainActivity must extend android.app.Activity even though I am not facing any issues in building a project but as I try to add the permission in androidManifest.xml it is not working
I had the same problem.
basically it can be fixed with a git command in your terminal...
git clean -xfd
so that's
-f to force untracked file deletion
-d to remove untracked directories
-x to remove untracked .gitignore files
It's possible you'll need to reconfigure your flutter and dart sdk paths, update your dependecies (flutter pub get / flutter pub upgrade) .
Be aware of that.
I found my solution here: Source
I want to open the Mule project from a repository folder that contains the project with the following folder structure.
I am doing this so I can commit the changes of the project straight to the repository (so others can also download the changes) without having to export and import the project as a zip file every time.
I am getting the following error message and Mulesoft also overwrites the mule.xml file to a blank file.
Is there anything I can do to avoid this from happening?
workspace print screen
option when importing
error message
You need to carry mule-project.xml, .classpath and .project files in the repository in case that you are not using Maven.
Please check / share your gitignore file. Also check the Error Log, there should be description of what is missing.
I'm working on a kotlin project that I want to execute as a jar. This is all done in IntelliJ Idea and I went about making the jar using the artifacts.
The process I followed was (as illustrated by an Idea guide):
Add artifact (as jar) from project structure
Build jar
Run jar
After this, I get a
'no main manifest attribute, in ____.jar'
What I have tried after reading several stack overflow questions:
Checking that the manifest file is in the correct folder and has the correct path in the artifact
Adding code to the build.gradle file for the jar->manifest portion
Trying the method of moving the manifest stuff into a resources folder
Checking that the jar exists
Moving the manifest stuff into a different folder (java,kotlin,out folders)
Making sure that the manifest file is in the correct format
All of the above has not worked.
Something that is confusing to me is that, even when I alter the manifest file to be in "incorrect" format, it still gives the same error. The path stated in the artifact's details is correct yet there is no difference even when I purposely input incorrect items in the manifest file. Not sure if that is the"real" problem but I'm also not sure how to fix that as well
None of the solutions worked for me.
I solved it in this way:
When setting up the artifact, change:
Meta-inf: (...)\src\main\ (you must remove "java")
Also, there was a problem with resources, solved this way:
When setting up the artifact:
Output Layout > Add copy of > Directory content > resources.
That's all!
For anyone that may have encountered this problem in intellij and did not find a solution in any other posts, what helped me was
Navigating to Project Structure
Going to the Artifacts tab
Explicitly adding a new META-INF/ directory in my jar
Adding the created MANIFEST.MF file to the META-INF/ in the jar FROM THE ARTIFACTS TAB
Rearranging the order for the META-INF/ to be at the top
Building and running
The end result looked like this
while creating the exeutable jar file explicitly create a mainfest.txt file
that should be in order of the directory structure and mainfest.txt file should contain only one line (Main-Class:name of the class containg main method)then run the jar tool
I have created the default play application in IntelliJ in directory P. I have over-written the default index.scala.html with my own html code. The html code refers to some css and js files which are outside the directory P. To include these external files, I added the directory of these files using project configuration settings.
My webpage doesn't load properly as the server returns 404 for the css and js files. What am I doing wrong?
When you added your directory using project structure, you only say:
Hey, IDEA, please consider this folder part of my project, consider
its contents source code and display it when I open my project.
However, when you deploy or run your app, you only deploy the usual folders to the server, which contain the resources which will be available for clients to access.
The external directory is not part of these directories and will not be deployed.
What you can do is to copy the file from the external directory as a part of your build process before deploying the application.
EDIT: Detailed answer here: What is intellij's build process for play applications
I have a project that I imported from a shared folder.
Everything worked fine until the hosting computer restarted
After the shared folder was back up I restarted Ti Studio, deleted the project, and imported it again, but it still wouldn't allow me to run the app.
Now there is an asterisk next to the project name so it looks like
this:
* ProjectName [master]
However, before the connection was lost it said [master + 1].
Also there's an asterisk next to app.js, and the background is red:
When I try to run it I get the following error:
[ERROR] : ** BUILD FAILED ** [ERROR] : The following build commands failed:
[ERROR] : Ld build/Debug-iphonesimulator/ProjectName.app/ProjectName normal i386
[ERROR] : (1 failure)
This application worked before I accidentally lost connection to the host folder.
I have also tried cleaning the project.
It seems like Titanium is trying to recover what I saved during the restart, so it won't allow me to run the project again.
TL;DR: How do I make Titanium Studio "forget" this project, and treat it like it's brand new?
UPDATE: I tried deleting the project and creating a new one with the same name, now all the files and folders have an asterisk next to them and the files have a red background. Next I'll try a new name...
UPDATE 2: Naming the project a new name didn't work either. Next I'll try creating a new project locally.
I had to create the project locally. For some reason, after losing the connection, Titanium couldn't hold a connection to the shared folder.
Edit: Here's what I did to get everything back to normal:
I deleted everything locally, on the shared folder, and from the workspace
I created the project locally
copied it to the shared folder
deleted the project from Ti Studio (didn't choose the option to delete the actual files)
then imported the project from the shared folder
Create a file in project root folder name it .gitignore
file contents:
.DS_Store
/app
/build
/plugins
/Resources
/platform
/i18n
build.log
build
CHANGELOG.txt
DefaultIcon-ios.png
DefaultIcon.png
iTunesConnect.png
LICENCE
LICENCE.txt
Manifest
MarketplaceArtwork.png
README
tiapp.xml
npm-debug.log
tmp
.map
.project
.settings
Thumbs.db