Error on compile to Andriod when apply certificate - codenameone

My app compile for android ok.
When I create the android certificate, and send to the codename compiler it don´t compile.
I tried to generate the certificate with the keytool and tried with the assitant on codenameone, the result is similar.
If I delete the keystore file and resend to the dashboard, the app compile ok.
This is the log errors
Note: there were 3 references to unknown classes.
You should check your configuration for typos.
(http://proguard.sourceforge.net/manual/troubleshooting.html#unknownclass)
Note: there were 1 references to unknown class members.
You should check your configuration for typos.
Note: there were 22 unkept descriptor classes in kept class members.
You should consider explicitly keeping the mentioned classes
(using '-keep').
(http://proguard.sourceforge.net/manual/troubleshooting.html#descriptorclass)
Note: there were 17 unresolved dynamic references to classes or interfaces.
You should check if you need to specify additional program jars.
(http://proguard.sourceforge.net/manual/troubleshooting.html#dynamicalclass)
Note: there were 5 class casts of dynamically created class instances.
You might consider explicitly keeping the mentioned classes and/or
their implementations (using '-keep').
(http://proguard.sourceforge.net/manual/troubleshooting.html#dynamicalclasscast)
Warning: there were 25 unresolved references to classes or interfaces.
You may need to add missing library jars or update their versions.
If your code works fine without the missing classes, you can suppress
the warnings with '-dontwarn' options.
(http://proguard.sourceforge.net/manual/troubleshooting.html#unresolvedclass)
Warning: there were 2 unresolved references to program class members.
Your input classes appear to be inconsistent.
You may need to recompile the code.
(http://proguard.sourceforge.net/manual/troubleshooting.html#unresolvedprogramclassmember)
Warning: Exception while processing task java.io.IOException: Please correct the above warnings
first.
:transformClassesAndResourcesWithProguardForRelease FAILED
:transformClassesAndResourcesWithProguardForRelease (Thread[Task worker for ':',5,main]) completed. Took 3.21 secs.
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':transformClassesAndResourcesWithProguardForRelease'.
> Job failed, see logs for details
* Try:
Run with --debug option to get more log output. Run with --scan to get full insights.
* Exception is:
org.gradle.api.tasks.TaskExecutionException: Execution failed for task
':transformClassesAndResourcesWithProguardForRelease'.
at

This has nothing to do with the certificate. It fails in the obfuscation stage before the certificate. These errors are notoriously hard to read and it seems you snipped it a bit too late. I need the section above that which includes the detailed warning about the class/method that isn't found.
Go to the error and scroll a bit higher and look for a familiar class name with a proguard warning next to it. This is the class causing a problem probably because of a missing dependency. If you can't find it just post the log link to the website chat and our support will look over that for you.

Related

Name Error __pyarmor__ not defined for code obfuscation

I have tried to obfuscate my python package using pyarmor
Example : pyarmor obfuscate <package_name>
Once the code has been obfuscated, I have build the docker image of the obfuscated code and deployed as docker container. But container throws error as Name Error: pyarmor not defined
I have checked out on the error and suggested that error might as below
No Bootstrap Code are executed before importing obfuscated scripts.
When creating new process by Popen or Process in mod subprocess or multiprocessing, to be sure that Bootstrap Code will be called before importing any obfuscated code in sub-process. Otherwise it will raise this exception.
If pytransform.py or pytransform/init.py raises this exception. Make sure it is not obfuscated, it must be plain script.
Also check system module os, ctypes, make sure they’re not obfuscated, try to use option --exclude to exclude the whole Python system library path.
can someone help to know what was the error and how to obfuscate py files and deploy in k8s or docker

React Native: Deprecated Gradle features ..., making it incompatible with Gradle 7.0

I'm getting this error. It all started when I tried to make use of react-native-camera and run my project
> Task :react-native-camera:compileGeneralDebugJavaWithJavac
> Task :app:mergeDexDebug FAILED
Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.2/userguide/command_line_interface.html#sec:command_line_warnings
252 actionable tasks: 33 executed, 219 up-to-date
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: C:\Users\joans\Desktop\Project\new_project\node_modules\react-native-camera\android\src\main\java\com\google\android\cameraview\Camera2.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
D8: Cannot fit requested classes in a single dex file (# methods: 65711 > 65536 ; # fields: 71075 > 65536)
com.android.builder.dexing.DexArchiveMergerException: Error while merging dex archives:
The number of method references in a .dex file cannot exceed 64K.
Learn how to resolve this issue at https://developer.android.com/tools/building/multidex.html
.....
* What went wrong:
Execution failed for task ':app:mergeDexDebug'.
> A failure occurred while executing com.android.build.gradle.internal.tasks.Workers$ActionFacade
> com.android.builder.dexing.DexArchiveMergerException: Error while merging dex archives:
The number of method references in a .dex file cannot exceed 64K.
Learn how to resolve this issue at https://developer.android.com/tools/building/multidex.html
Please, any suggestions would be helpful

Eazfuscator.NET error for custom build configuration

I’m using Eazfuscator for a while for my project and everything is working as it should be until, I created a copy of Release build configuration called “Release-Internal”. I also updated the post build event and changed the script to “if /I "$(ConfigurationName)" NEQ "Debug"...". Now all of my projects obfuscate without any problems but only one of them displays the following error:
(EF-1099 error occurred.
4> Obfuscator can not load the input assembly or one of its
dependencies.
4> To resolve this issue you can:
4> - Specify a probing path
4> - Put a missing assembly near the input file
4> More information can be found in Eazfuscator.NET Documentation at
4> Troubleshooting -> Error Codes Knowledge Base -> EF-1099 chapter.)
The interesting part is if I change the active configuration to “Release” the same project obfuscates without any problems. The difference between the “Release” and “Release-Internal” configurations are just that the “Release-Internal” has an extra conditional compilation symbol called INTERNAL.
I also build the project without obfuscation with the “Release-Internal” config. The application build succeed and executed as it should be.
Best regards,
From the build output, it seems you are building projects in parallel.
I'm thinking there's a missing dependency at the time Eazfuscator.NET tries to load your assembly.
I recommend trying to set the "maximum number of parallel project builds" to 1 in Visual Studio IDE > Tools > Options > "Projects and Solutions" and try again.
The event viewer may have some more information (ex. side-by-side errors).
You can also try to enable assembly bind failure logging to try to identify which specific dependencies could not be found. See: How to enable assembly bind failure logging (Fusion) in .NET
It could be as simple as setting "Copy Local" to true in the project's reference properties of the missing dependency.
You can read the "EF-1099: Unable to load input assembly, reflection load failed" help topic in "Eazfuscator.NET Documentation.chm" > Troubleshooting > Error Codes Knowledge Base. The help document for Eazfuscator.NET 3.2.278.32704 has "Instructions on enabling the architecture-neutral loading mode of Eazfuscator.NET" in the same help topic.

Google app engine error, don't know where to start looking

I'm receiving this error when I attempt to start an app using google app engine :
Loading modules
com.bookmark.Mobile_bookmark
[ERROR] Unable to find 'com/bookmark/Mobile_bookmark.gwt.xml' on your classpath; could be a typo, or maybe you forgot to include a classpath entry for source?
[ERROR] shell failed in doStartup method
I don't have a file called Mobile_bookmark.gwt.xml. My project name is mobile-bookmark
Why is this error occuring ?
If it's looking for Mobile_bookmark.gwt.xml (the wrong file), I'd check how you are starting the server.
For example, under Eclipse, I'd check run configurations --> arguments to see if "Mobile_bookmark" got into there. (you can get to run configurations by selecting the little triangle next to either the green debug or run button you use to start it --- or RUN (menu in eclipse) -- run configurations -- select your project)
Change the file name to whatever *.gwt.xml file you do have. I suspect it's mobile-bookmark.gwt.xml.
Look under /src/yourpath/yourproject/
Your layout is probably like:
/src/yourpath/yourproject/*.gwt.xml
/src/yourpath/yourproject/client
/src/yourpath/yourproject/server

java.lang.IllegalArgumentException thrown at debug launch in Eclipse CDT

I am using Eclipse CDT, with MinGW and under Windows XP, to developp a little C program exporting itself as a JNI-compliant DLL.
Debugging the program from the Java calls is not easy, and thus I added a "Debug" configuration to my project and a main method that tests some functions.
When I launch the debug, i get this weird Java error :
An internal error occurred during: "Launching NuanceWrapper.exe".
java.lang.IllegalArgumentException
It seems very much like it is an internal Eclipse problem. I got the stacktrace of the exception in the .log file of the .metadata folder :
!ENTRY org.eclipse.core.jobs 4 2 2011-02-04 14:08:31.531
!MESSAGE An internal error occurred during: "Launching Wrapper.exe".
!STACK 0
java.lang.IllegalArgumentException
at org.eclipse.osgi.framework.internal.core.PackageAdminImpl.getBundles(PackageAdminImpl.java:571)
at org.eclipse.core.internal.runtime.InternalPlatform.getBundle(InternalPlatform.java:181)
at org.eclipse.core.runtime.Platform.getBundle(Platform.java:1416)
at org.springframework.ide.eclipse.core.BundleStateLocationVariableResolver.resolveValue(BundleStateLocationVariableResolver.java:32)
at org.eclipse.core.internal.variables.DynamicVariable.getValue(DynamicVariable.java:54)
at org.eclipse.cdt.internal.core.cdtvariables.EclipseVariablesVariableSupplier$EclipseVarMacro.loadValue(EclipseVariablesVariableSupplier.java:103)
at org.eclipse.cdt.internal.core.cdtvariables.EclipseVariablesVariableSupplier$EclipseVarMacro.getStringValue(EclipseVariablesVariableSupplier.java:90)
at org.eclipse.cdt.dsf.gdb.launching.LaunchUtils.getLaunchEnvironment(LaunchUtils.java:385)
at org.eclipse.cdt.dsf.gdb.launching.LaunchUtils.getGDBVersion(LaunchUtils.java:281)
at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.getGDBVersion(GdbLaunchDelegate.java:243)
at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launchDebugSession(GdbLaunchDelegate.java:129)
at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launchDebugger(GdbLaunchDelegate.java:83)
at org.eclipse.cdt.dsf.gdb.launching.GdbLaunchDelegate.launch(GdbLaunchDelegate.java:72)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:853)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:702)
at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:923)
at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1126)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Any idea what could be the problem ? I really need this debug functionality in order to understand what is wrong in my code.
Thank you for your answers.
I looked at the source code of the different files of your stack trace, and it seems to be a problem with your CDT project's configuration. You should check the settings here and try to change them.
One of the CDT build variables seems to be wrong. In LaunchUtils.java, line 390, var.getStringValue() is causing the issue because in this variable (var), which contains a name and an associated value, the value is null.
Hope this helps.
Had the same problem. the next string from the exception stack trace:
at org.springframework.ide.eclipse.core.BundleStateLocationVariableResolver.resolveValue(BundleStateLocationVariableResolver.java:32)
led me to the idea that SpringSource ToolSuite (or Spring IDE) could cause the issue. After uninstalling it and all its components the problem was gone.
Hope this helps.

Resources