title: Dealing with shared preferences stored in a library
body: <p>I have an app that has a free, and a paid version. I put all the free version code into a library, which I reference from a new free version project, and the paid version project. </p>
  
  <p>I noticed that the library, and now my projects all have a properties file, and my preferences stopped working completely. It seems that depending on what namespace the code executes in, it gets a different result when you query for SharedPreferences.</p>
  
  <p>What is the best way to deal with this? Both apps have the same preferences as of now, but I will probably extend the paid version later and add preferences that don't exist in the free version.</p>