I have an android project named SimpleVideoEditor, and I would like to submit it into F-Droid. So I was following this CONTRIBUTING.md tutorial by F-Droid. Now in the building-it subsection, they say
Make sure that `fdroid lint app.id` doesn't report any warnings. If it does, fix them.
So I tried $ fdroid lint com.fahimfarhan.simplevideoeditor and it gave me this error:
Error
com.fahimfarhan.simplevideoeditor: Build generated by `fdroid import` - remove disable line once ready
At first I didnot even know that this is an error and so I submitted my app. But later I got an Email that says my build failed. So I am trying to fix it.
What does this error even mean? I don't understand how to fix this issue. I did Google but the search result doesnot make any sense. Sorry for not including anything else because this is all I have. I am confused.
Could anyone help me?
I found the fix to this problem.
Their must be a line inside build in your yaml file which might be something like this.
disable: Generated by import.py - check/set version fields and commit id
You have to remove this line and then you will pass all the lint errors. Your builds list should look something like this.
Builds:
- versionName: '2.0'
versionCode: 2
commit: commitId
subdir: app
gradle:
- yes
The auto generated looks something like this -
Builds:
- versionName: '2.0'
versionCode: 2
disable: Generated by import.py - check/set version fields and commit id
commit: '?'
subdir: app
gradle:
- yes
Remove the disable line and add the commit and you will be good to go.
Related
My android app is filling up the logs with messages like this (making logcat almost useless):
W ResourceType: For resource 0x7f1001b5, entry index(437) is beyond type entryCount(157)
The resource ID changes from line to line, as well as the index and entryCount numbers.
This issue only happens on release builds. I know it happens on Android 7.0, 7.1, and 8.0. I have seen some logcats from Android 10 where I do not have the issue.
My app targets sdk 30, with minSdk 24. I have multiDexEnabled true. Compile with Java 8 (1.8). Written 100% in Kotlin.
There are some similar questions, without any answers that work for me, here, and here, and here
I tried aapt dump --values resources myAPK.apk > c:\my-res.txt mentioned in one of the answers which gives me enough info that I can see it has to do with theme I'm using, which is Theme.AppCompat.DayNight.NoActionBar
I already set vectorDrawables.useSupportLibrary = true in gradle
I don't know where to look or what to try from here.
Any pointers on how I might be able to fix it so I don't get those entries in my log?
Update:
I have not confirmed a 100% but it seems this only happens to apps installed through Play Store that are uploaded by .aab file. When I upload .apk I'm starting to think the issue is gone. But I'll need to wait a bit longer and make sure.
In case of creation of the blank project in AIDE on a pad 4.2.2 of the basic code, AIDE finds an error:
This method must return the value of type"
Also QuickFix suggest to correct it by 'return 0' adding before a penultimate bracket that in turn attracts besides an error
A void method can't return a value
Also suggests to remove digit 0. Application is compiled, but not launched, referring to an error in application...Any ideas, why is it so? AIDE versions I tried the different.
I had the same error and when i reinstalled the app it worked. Also make sure you dont have a patched apk. I had that error with a pirate patched apk. I installed the original app with the premium key apk. XD Hope this helps you!
I hit this error and found no hits for the error message, so I thought I'd share the solution I came up with to save anyone else facing the problem repeating my work.
When writing a new Android library (apklib) for use in a (large) application, I'm getting the following error during dexing when I add my new project as a dependency:
trouble writing output: Too many field references: 70185; max is 65536.
You may try using --multi-dex option.
References by package:
<...long list of packages with field counts elided...>
The particular build step it fails on is:
java -jar $ANDROID_SDK/build-tools/19.0.3/lib/dx.jar --dex \
--output=$PROJECT_HOME/target/classes.dex \
<... long list of apklib and jar dependencies elided ...>
Using --multi-dex as recommended by the error message might be a solution, but I'm not the owner of the application project and it already has a large complex build process that I would hesitate to change regardless.
I can reproduce this problem with a no-op test library project that has literally no fields, but in the error output it's listed as having 6000+ fields. Of the packages listed in the error output, there are a handful with similar 6k+ field counts, but then the vast majority have more plausible <1k field counts.
This problem is similar to the "Too many methods" problem that Facebook famously hacked their way around. The FB solution seems insane, and the only other solutions I've found (e.g., this Android bug ticket, or this one, this SO answer, this other SO answer) all involve changing the main app's code which is well beyond the scope of what I want to do.
Is there any other solution?
The solution was to change the package in the AndroidManifest to match the main application's package.
A manifest like this:
<manifest package="com.example.testlibrary" ...
resulted in 6k+ fields and build failure. Changing it to match the main application's package
<manifest package="com.example.mainapplication" ...
resulted in the project building successfully.
Note that only the package in the manifest is changing, I did not make any changes to the library's Java source or its layout (the Java package was still com.example.testlibrary with directory structure to match).
I hypothesize that the different package name is causing all the Android fields to be included again under that package. All the packages in the error listing with 6k+ fields had a different package name than the main application.
I also (later, grr), found this blog post which details the same problem and the eventual same solution.
I am not sure if it is Android Studio ( 0.1.9 ) or AndroidAnnotation problem, however, lately I cannot make and compile my AndroidAnnotations projects.
Ok, so I try to make project and this is what I got in "Messages" window:
Information:Round 1:
Information: input files: {com.antyzero.sidereelo.ui.activity.SplashActivity}
Information: annotations: [com.googlecode.androidannotations.annotations.EActivity, java.lang.Override]
Information: last round: false
Information:Processor com.googlecode.androidannotations.AndroidAnnotationProcessor matches [com.googlecode.androidannotations.annotations.EActivity] and returns true.
Information:Note: Starting AndroidAnnotations annotation processing
Information:Round 2:
Information: input files: {com.antyzero.sidereelo.ui.activity.SplashActivity_}
Information: annotations: [java.lang.Override]
Information:Processor com.googlecode.androidannotations.AndroidAnnotationProcessor matches [] and returns true.
Information:Round 3:
Information: input files: {}
Information: annotations: []
Information: last round: true
Information:Compilation completed successfully with 1 warning in 17 sec
Information:0 errors
Information:1 warning
Warning:: Unclosed files for the types '[dummy1372862415557]'; these types will not undergo annotation processing
Nothing less, nothing more. In result I don't have my SplashActivity_ created. This message is from brand new project but my old projects are also affected.
Answer from Android Studio: Use AndroidAnnotations is not helpful.
I was working with AA and IntelliJ weeks before Android Studio without problem. IMO it might happen after latest Android Studio update, but maybe there is some kind of solution for this right now, if not I will report this to Android Studio team. Thanks for help.
One more thing. My projects are using Maven and building them from CLI works fine, all classes are generated as they should be.
I was facing the same problem when trying to inject a view with #ViewById, and the problem was that I was declaring the field private. Declaring it at least protected fixed the issue!
Before:
#ViewById
private NoListResultsView noResultsView;
After
#ViewById
protected NoListResultsView noResultsView;
I read alot of posts similar to this topic, but cant solve it anyway.
Everytime I try to export my signed application with the obfuscator enabled, I get the following:
[2011-12-23 13:26:35 - AppName] Proguard returned with error code 1. See console
[2011-12-23 13:26:35 - AppName] proguard.ParseException: Unknown option 'android\AppName\proguard\dump.txt' in argument number 9
[2011-12-23 13:26:35 - AppName] at proguard.ConfigurationParser.parse(ConfigurationParser.java:170)
[2011-12-23 13:26:35 - AppName] at proguard.ProGuard.main(ProGuard.java:491)
I use the Google APIs Version 2.3.3 and the standard configuration and just added the proguard.config=proguard.cfg to the projects.properties.
I use "Progra~1" in the SDK path and tried clean already.
As far as I know, the dump.txt is generated in a successfully run of the obfuscator.
Can someone give me a hint?
It is because of the space in the project folder path. There is a duplicate question here Proguard ParseException with Default proguard.cfg on Android and the answer is step 2,3,4 and 5 of the accepted answer.