how to include ACRA in ProGuard rule file - proguard

i am configuring ProGuard for the entire Project.
When i try to run the App .apk file got generted successfully.
I get following exception in the line of ACRA initialization.
java.lang.NoSuchFieldError: PUT
at java.lang.Class.getDeclaredAnnotation(Native Method)
at java.lang.Class.getAnnotation(Class.java:243)
at cjw.a(SourceFile:124)

Check your Proguard config to make sure it includes that outlined at:
https://github.com/ACRA/acra/wiki/Proguard
And if that doesn't fix it then post
your ACRA config
your Proguard config

Related

How do I use swagger-codegen cli with custom template?

I would like to add a few tweaks to the typescript-fetch template.
I have downloaded the typescript-fetch folder linked above and stored it in .\template folder in my project. I assumed that all I would have to do is pass --template-dir .\template to the CLI as follows:
>Java -jar .\bin\swagger-codegen-cli.jar generate -l typescript-fetch -i https://localhost:7113/swagger/v1/swagger.json -o output -Dio.swagger.v3.parser.util.RemoteUrl.trustAll=true --template-dir .\template
but getting the following exception:
07:55:44.212 [Thread-1] INFO i.s.codegen.v3.AbstractGenerator - writing file c:\projects\trustwell-api-client-ts\output\index.ts
Exception in thread "Thread-1" java.lang.RuntimeException: Could not generate supporting file 'SupportingFile:
templateFile: api.mustache
folder:
destinationFilename: api.ts
'
at io.swagger.codegen.v3.DefaultGenerator.generateSupportingFiles(DefaultGenerator.java:666)
at io.swagger.codegen.v3.DefaultGenerator.generate(DefaultGenerator.java:789)
at io.swagger.codegen.v3.cli.cmd.Generate.run(Generate.java:388)
at java.lang.Thread.run(Unknown Source)
Caused by: com.github.jknack.handlebars.HandlebarsException: c:\projects\trustwell-api-client-ts\.\template\api.mustache:142:73: found: '-last', expected: 'no viable alternative at input '{{^-last''
? configuration.accessToken("{{name}}", [{{#scopes}}"{{{scope}}}"{{^-last}}, {{/-last}}{{/scopes}}])
^
at com.github.jknack.handlebars.internal.HbsErrorReporter.syntaxError(HbsErrorReporter.java:93)
at com.github.jknack.handlebars.internal.antlr.ProxyErrorListener.syntaxError(ProxyErrorListener.java:41)
at com.github.jknack.handlebars.internal.antlr.Parser.notifyErrorListeners(Parser.java:544)
...
It seems that CLI is picking up my folder, but I'm not sure if there is anything else I need to do to make this work.
Question: how can I run swagger-codegen CLI with local mustache templates?
The solution was to use templates from here:
https://github.com/swagger-api/swagger-codegen-generators/tree/master/src/main/resources/handlebars/typescript-fetch
I don't understand the distinction, and I suspect the two might get out of sync at some point, but it works.

Neovim gkeep plugin

I installed gkeep plugin for Neovim (https://github.com/stevearc/gkeep.nvim) and didn't like it. I removed it from my plugins (I use vim-plug) and run :PlugClean after that. But now I can't open neovim without error mentioning that gkeep plugin. How to fix this?
Error detected while processing function remote#define#request:
line 2:
Error invoking '/home/daniil/dotfiles/nvim/plugged/gkeep.nvim/rplugin/python3/gkeep:autocmd:BufEnter:*'
no request handler registered for "/home/daniil/dotfiles/nvim/plugged/gkeep.nvim/rplugin/python3/gkeep:
It's pointing to ~/dotfiles/nvim because I created symbolic link from ~/dotfiles/nvim to ~/.config/nvim.
Also, there is no directory gkeep.nvim inside plugged folder.
UPD: and this is my plugins
It seems that you haven't removed the configuration related to gkeep.nvim. Try to remove all settings related to gkeep.nvim.
Also, when you open neovim, run the command :UpdateRemotePlugins. It should solve your issue.

Could not initialize class jmeter HTTPHC4Impl

When I try to run my api test on jmeter, this error occurs: Uncaught Exception java.lang.NoClassDefFoundError: Could not initialize class org.apache.jmeter.protocol.http.sampler.HTTPHC4Impl in thread Thread[Thread Group 1-10,6,main]. See log file for details How can I solve it?
Sounds like your JMeter installation got corrupt somehow, double check that you have ApacheJMeter_http.jar file under "lib/ext" folder of your JMeter installation and the .jar file contains the needed class.
If the .jar is not there I would recommend either downloading the appropriate version from the above website or install/reinstall jmeter - HTTP Protocol Support plugin using JMeter Plugins Manager

Activator bundle throwing null pointer exception

I am facing a unique problem - the following code block throws NPE only when my plugin is packaged and deployed not when I am launching it as an 'Eclipse Application'
inputStream = Activator.getDefault().getBundle().getEntry(templateFilePath).openStream();
I have tried other variations as well but nothing is working :
inputStream=Platform.getBundle("SuitACore").getEntry(templateFilePath).openStream();
Here templateFilePath is a file resource being read from a directory in plugin.
Thanks Nick , greg-449
I extracted the packaged jar - the template folder resource was not getting included. I changed this option from build.properties and now this works!

Failed to load late-bound plugin: org.apache.maven.plugins:maven-resources-plugin

We have our local Maven repository which was working fine till yesterday.
Today we are getting the following error while building any project.
Failed to load late-bound plugin: org.apache.maven.plugins:maven-resources-plugin
We haven't change any settings. Any idea?
It's hard to say because you skipped the next line that prints the Reason. A typical output looks like:
[WARN] Failed to load plugin: org.apache.maven.plugins:maven-resources-plugin. Adding to late-bound plugins list.
Reason: Failed to load plugin. Reason: The plugin 'org.apache.maven.plugins:maven-resources-plugin' does not exist or no valid version could be found
It would have been interesting to join this line to find a fix for the root cause of the problem.
I resolved it.
I had to delete the plugins folder on my local repository then Maven downloaded the plugins again.
It works fine now.