For some stupid reason android studio decided to start failing generating signed APK always if I dont manually enter the password each time. now it just started happening around maRCH-june this year(cant remember exactly when), until then I always just pressed next->next->finish cause i ticked the Remember passwords checkbox and everything worked great, but suddenly it started failing.
I tried generating once without checkbox and then generatin again with it
I even tried on a different computer but it still happens
If i dont enter the password manually each generation and rely on the remembered password it will always fail, even if the last generation I enetered the correct password and it generated successfuly, meanwhile entering the password each time works aslong as the password is right(like it should)
anyone knows how to fix this problem? while not stopping me from generating signed APK its annoying as hell
In my case it was caused by Windows 10 Controlled folder access. Try adding folder with the encryption key file to exceptions list or turn Controlled folder access entirely off.
Related
My crypdata password is broken, the same password that i am using suddenly stopped working. How to fix it?
I thought the problem is Capslk. So i tried with capslk and every character of password. Still no solution. It seems to be impossible to fix it. Cuz i can only switch laptop off/on and can write a password and nothing more.
I've just changed our authentication methods for connecting via SSH as we're moving into production for our app, we're also in the middle of migrating to EC2#AWS.
Its been a few days now and I've started to notice a few little changes whcih seem small but none the less, causing me to make mistakes as we run through command lines.
We disabled root logins to start with and now working on a range of users, all with different keys etc.
We no longer get our login 'introduction' when we login. We had some pretty useful information on there which we enjoyed reviewing - Where is that stored and how do we get it back or rebuild it?
We cant 'tab' to autocomplete the filenames anymore. This probably saves us tens of hours a week in typing so would be nice to get this back.
Im sure theres a configuration file somewhere but the files I've reviewed give little to no clue on either of these issues.
While trying to get GitLab Kanban Board to run nicely with my GitLab server I somehow managed to get myself locked out of the latter. Whenever I open the GitLab-URL now there's the message "No authentication methods configured" and no option for logging in.
Unfortunately, I don't even remember the exact settings that I was messing around with at that time, because it was a while ago and it's only now that I found the time for dealing with this problem again. IIRC one of the last things I did was to try and get OAuth working. (And I think that I was changing some settings in the web interface last, not in the settings files.)
Unable to find a solution online, one of the things I tried was to do a backup and then restore that on a different server. But the result is that I then get the same message on the new server also.
Does anyone have any idea on how to recover from this situation? Is there any way for example to enable "normal" login again by changing settings in the database?
If it's not (easily) possible to recover the whole GitLab installation, is there some way to somehow at least extract the bug report data from it? That's the data that I would be most unhappy to loose...
I'd really appreciate any help, because I'm completely at a loss right now!
You can use the Rails console to reenable your sign-in.
sudo gitlab-rails console
s = ApplicationSetting.find_by(signin_enabled: false)
s.signin_enabled = true
s.save
This will modify the rails settings directly.
As of version 10.5.X, use this instead (different ApplicationSetting key)
sudo gitlab-rails console
s = ApplicationSetting.find_by(password_authentication_enabled_for_web: false)
s.password_authentication_enabled_for_web = true
s.save
Have a simple task, but I just cannot find the quick work around, or maybe I just don't have all the info.
I have a solution (VS2012 Pro) for a SSIS project, which contains lots of dtsx packages.
When I first open the solution it pops up the enter password screen, which I want to get rid of, of course knowing the password.
My question is, is there necessary to get to the proprieties tab of each and every dtsx package and remove the password, or is there a "master setting" for the hole project? Or should I use an application which should remove the password from a command line?
Regards,
If you have a lot packages to update, I would suggest you to write a script to do it in a batch.
what I did couple years ago, I created a c# project, process each ssis package, udpate pass word and then save the package. it works fine.
API: https://msdn.microsoft.com/en-us/library/microsoft.sqlserver.dts.runtime.package.aspx
example: https://github.com/guoliang-dev/ssis-utils/blob/master/SSISHelper/com/liguoliang/ssis/util/DtsUtils.cs
I've just got rid of the annoying password, but the hard way. Although, the project had a security option setting, it notified me after changing it that I should manually check each and every package in order to match the security setting with the project one.
In my j2me app that is signed by veriSign, has problem in accepting the always or yes permissions the time it has to perform PIM.getInstance().openPIMList(..) action.
When my app perform below line of code very first time of it's installation it hangs and doesn't show up the main screen rather a black background hanged screen. When I exit and restart the application it runs normally without any problem even if I delete it and put it back again and runs fine, except I delete and restart the phone and try to run it again it shows the same problem I described above.
My code of line that causes to ask permissions is here that actually also causes the problem. One more thing this error only occurs on specific phones which actually allow ALWAYS permission on start.
I am checking it over Nokia X2-05 and it shows problem but on Nokia C3-02 it doesn't as it doesn't allow ALWAYS permission automatically on start of app.
private void permissionSettings() throws PIMException {
PIM.getInstance().openPIMList(PIM.CONTACT_LIST, PIM.READ_WRITE);
}
Above is code snippet that hangs at first start.
It sounds like a bug on the handset to me, the TCK tests used to verify j2me libraries are pretty weak so lots of bugs like this find their way through.
It seems that the key is in the permissions, so I would try and play around in this area. Make sure you have the right permissions set in the .jad (before signing), if you can get hold of one try to sign with a certificate in a different security domain or certificate, try changing the permission level before running the applet.
I would expect that you'll only be able to work around the problem, so rather than suggest something specific I would be varying things within those areas.