Find my lost Android app signing key from IntelliJ

Over time I seemed to have lost my keystore password, that I needed to sign some Android app. Still had the keystore file though. IntelliJ also had the keystore password stored. So how do I get the password from IntelliJ?

There is a handy utility on github for this https://github.com/corneliudascalu/intellij-decrypt. If you have the master password for IntelliJ, it decrypts all passwords stored in IntelliJ. Using this I was able to recover the signing password for my keystore.

This requires the security.xml file from IntelliJ where the passwords are stored. Where is this stored on OSX? Googleing for it, this seems to vary. None of the given options seem to make an sense. So we try “find / -type f -name security.xml”. This finds it in “/Users/myname/Library/Preferences/IdeaIC14/options/security.xml”. That’s how I finally got the keystore password.

Originally published at swenotes.wordpress.com on May 28, 2015.

Lost Android app signing key from IntelliJ? was originally published in snajdr.de on Medium, where people are continuing the conversation by highlighting and responding to this story.

Google provides command line tools for those (firebase-cli an workbox-cli), which makes live super easy. But since you stumbled across this article, you propably already try to use them.

There are several commands such as firebase serve or workbox inject:manifest (pretty basic ones) which led my terminal window to freeze completely, not even Ctrl+C was working anymore.

Solution:

It seems to be a bug with nodeJS Version 8.1.0. Changing the version to another one, using nvm for instance, solved it.

firebase-cli or workbox-cli freeze terminal was originally published in snajdr.de on Medium, where people are continuing the conversation by highlighting and responding to this story.

Since it is written in PHP, hosted on GitHub, setting up a new shop by cloning from Shopware’s GitHub sounds like no big deal at first and it is quite easy indeed, but there are some hidden traps.

Basically you have to follow the steps also mentioned in their GitHub-Readme in the section called “Start Hacking”. I am going through the following steps, altering some of the recommended and adding some more:

1) Get your copy

There are two main-approaches of getting the files into your project. Which one to use depends on your personal favor, but also on the Git Hosting Service you or your company is using.

1a) Use your own fork

If you are using GitHub, this is the way to go. Fork the repository and clone it on your local machine.

git clone git@github.com:[YOUR USERNAME]/shopware-4.git

1b) Use an additional remote and branch

If you don’t use GitHub and prefer hosting your repositories on your own server or for example at Bitbucket (as I do), you can’t fork a GitHub-Repo. So you have to clone it onto your local machine and add some additional remote and branch to achieve something comparable.

First clone the original repo.

git clone https://github.com/ShopwareAG/shopware-4.git

Add a new remote and push.

git remote add myrepo git@bitbucket.org:myusername/myrepo.git
git push myrepo master

Add and checkout your branch.

git branch mybranch
git push myrepo mybranch
git checkout mybranch

Using this method you can merge a new Shopware version into your branch from the original Shopware Repo at any time without having to merge anything by hand.

2) Build/seed Database

Now it’s time to create your config files, build and seed the database. I’m not going into details about the config files here, I think you’ll manage this by yourself, if you did it up to here.

To build and pre-fill the database use the provided script in the build-directory.

php build/ApplyDeltas.php

On a server environment you may prefer using Apache Ant for creating config and database as Shopware provides scripts for this as well. I’ll cover this in another post in the future.

Until now almost everything goes according to Shopware’s Readme and at this point you have your shop up and running (if you have configured your webserver etc., which I assume). Yay! Start coding, theming, skinning and go crazy…

BUT WAIT! As soon as you try to install plugins from the Shopware Community Store, even those which come preinstalled like PayPal, or try to update existing plugins you’ll run into some strange errors sooner or later, with not really helpful error messages such as “Given file is no zip archive”. I explained the issue in more detail in this (german) post at the Shopware forum: http://forum.shopware.de/post81016.html#p81016

But you can solve this issue by a simple step:

3) Set your version

As mentioned in the forum post these problems are caused by a missing version number in /engine/Shopware/Application.php. In this file, there is only a placeholder ____VERSION____, which is presumably replaced by hand, when the Shopware crew is wrapping up a new release build.
So to fix this error, simply replace the placeholder with a valid version number and you are set:

…
class Shopware extends Enlight_Application
 {
 const VERSION = ‘4.1.4';
 const VERSION_TEXT = ‘’;
 const REVISION = ‘201312061433';
…

With this fix you can use the whole Plugin-Management without any problems.

This post was originally published on my blog on 23rd of february, 2014.

Setting up Shopware from GitHub was originally published in snajdr.de on Medium, where people are continuing the conversation by highlighting and responding to this story.

This year’s push conference again was packed with really inspiring and entertaining talks more less closely related to UX topics.

This is my personal list of favorites, the talks, I will tell my friends about, the talks, that made me laugh, think, made me proud and humble and motivated me the most.

In order of appearance.

Truth is contextual Or: The holy grail of process and collaboration

Scott Savarie / Product Manager @ InVision

Scott Savarie, product manager at InVision jump-started the push conference with his entertaining talk about the hard role of a designer nowadays due to an abundance of tools and processes and roles. By the way, if you don’t know Invision, it’s one of the leading prototyping design tools out there.

Scott is really struggling, when his mom asks him what his job is. There are no clearly defined roles anymore:

Hank on Twitter

Scott Savarie #push16

He tells us, that there is not the one and only holy grail, the one solution which suits all problems. He rather recommends to stop reinventing and start standardizing, creating guidelines to lead others instead of doing everything by yourself, his example is the module library used by Facebook.

Doreen on Twitter

Nice first talk from Scott Savarie at #push16

Also he encourages designers, to be more pushy, asking more questions, challenging ideas and products and becoming the killjoy from time to time.

His third advice is not just to rely on your talent and gut feeling, but use data and evidence as well, reflect your opinions.

Include designers in bigger questions and do not let them only push pixels around!!!

The psychology behind successful products

Nathalie Nahai / Web Psychologist @ The Web Psychologist Ltd.

If you think psychology is something weird and boring, something for the Woody Allen maybe, you have definitely missed Nathalie Nahais talk, which turned psychology in one of the most interesting subjects ever.

According to her, seven points make a product successful. The seven points are:

1. Endowed Progress
2. Sunk-cost fallacy
3. Appointment dynamic
4. Cognitive load
5. Processing fluency
6. Hedonic adaptation
7. Dopamine loops

For more information look at her awesome slides.

Trust Me: UX for Privacy

Ame Elliott / Design Director @ Simply Secure

Ame is talking about the power of UX design to protect people’s privacy. She says, security has to be easy and intuitive or it won’t work. This is the main challenge for UX designers — finding the appropriate complexity for privacy and security.

On the one hand it’s about helping more people to understand the systems the are using and the imposed threats. And then it’s also about motivating a behavior change towards more secure behaviors.

Check out her slides here.

Articulating Design Decisions

Tom Greever / UX Director & author of Articulating Design Decisions @ Bitovi

This talk inspired me so much that I bought Tom’s book right after he had finished it. So maybe I’m the best proof that he actually knows what he’s talking about his topic, how to sell your design decisions to your clients.

The main three questions a designer should know answers to are:

1. What problem does this solve?
2. How does this affect the user?
3. Why is it better than the alternative?

And if this doesn’t work out — paint a duck… What? A duck? Yes… watch Toms talk at vimeo to find the duck:

Smart Transitions in UI Design

Adrian Zumbrunnen / UX Designer @ Freelance at Google

Adrian from Switzerland got us all with his bar of swiss chocolate he pulled out while distracting everyone of us with some fancy animations in his slides.

Packed with interesting examples and helpful insights he fascinated the audience in no time making this one of the best talks of the whole conference.

Get yourself a piece of chocolate at vimeo:

My favorite talks from push conference 2016 was originally published in snajdr.de on Medium, where people are continuing the conversation by highlighting and responding to this story.

Which sounds nice (and actually is) may cause some problems in some cases, especially if you are using AngularJS.

You can solve this problem by modifying your asset configuration in config/environments/production.rb like this:

config.assets.js_compressor = Uglifier.new(:mangle => false)

Hint: Just changing this setting in an heroku environment won’t recompile (or re-precompile) your assets as this is only happening after they changed.

Source: http://blog.berylliumwork.com/2013/07/tips-on-rails-4-assets-compression-with.html

AngularJS with Rails4 Asset Pipeline was originally published in snajdr.de on Medium, where people are continuing the conversation by highlighting and responding to this story.

Ready to deploy and run NodeJS Server to serve static files from heroku built with grunt.

What’s in it

• NodeJS Express to serve static files from build-directory
• Optional HTTP Auth (uncomment lines in server.js)
• Grunt Task to build SCSS, Javascript and Kit-Files (What is kit?)
• Grunt LiveReload included

How to use

First, create a new heroku app

heroku create heroku-node-static-express —region eu

Then push your repo to heroku

git push heroku master

It’s up an running! Almost…

Because…

Not a single grunt task has run! So basically no CSS files, Javascript or compiled HTML documents exist.

You can run the grunt task manually:

heroku run grunt

This works fine, but it’s not quite handy when you have to do this everytime you push a new commit to heroku.

Using a custom buildpack you can do this automatically after pushing a commit.
I use the customized Heroku Buildpack with Grunt support by Matthis Buchetics, you can find it at https://github.com/mbuchetics/heroku-buildpack-nodejs-grunt.

Adding it to your heroku app is easily done by adding some environment variables:

heroku config:set BUILDPACK_URL=https://github.com/mbuchetics/heroku-buildpack-nodejs-grunt.git
 heroku config:set NODE_ENV=production
 heroku config:set PORT=80

That’s it! Now, everytime you push a commit, your default grunt task is executed.

Serve static HTML files build with grunt from heroku was originally published in snajdr.de on Medium, where people are continuing the conversation by highlighting and responding to this story.

…didn’t know this :-|

It’s as easy as this:

sudo update-alternatives — config editor

Thanks to HowToGeek!

Change the Default Editor From Nano on Ubuntu Linux was originally published in snajdr.de on Medium, where people are continuing the conversation by highlighting and responding to this story.

To achieve this, first of all create a custom class for your action derived from RailsAdmin::Config::Actions::Base. I prefer putting it into /config/initializers/rails_admin.rb.

module RailsAdmin
  module Config
    module Actions
      class MyAction < RailsAdmin::Config::Actions::Base
        RailsAdmin::Config::Actions.register(self)
        register_instance_option :visible? do
           true
        end
        register_instance_option :member do
          true
        end
        register_instance_option :link_icon do
          #FontAwesome Icons
          'icon-check'
        end
        register_instance_option :controller do
          Proc.new do
            # Do whatever you want with @object
          end
        end
      end
    end 
  end
end

Then, add your new action to the RailsAdmin config, like this:

RailsAdmin.config do |config|
 # …
  config.actions do
    dashboard # mandatory
    index # mandatory
   # …
    my_action do
      # Make it visible only for specific model.
      # You can remove this if you don’t need.
      visible do
        bindings[:abstract_model].model.to_s == `MediaTarget`
      end
    end
  end
end

That’s it!

Custom Actions for Rails_Admin was originally published in snajdr.de on Medium, where people are continuing the conversation by highlighting and responding to this story.

Visit bleech.io for an amazing collection of useful and inspiring links for creative web workers.

bleech.io was originally published in snajdr.de on Medium, where people are continuing the conversation by highlighting and responding to this story.