IssueTracker

I have had this problem also.  I released the free version of my application and
thought that I had set the sharedUserId in preparation for later releasing the paid
version of my application.  I needed to be able to copy the database from the free
version to the paid version, so I set the sharedUserId.  However I followed the
instructions for sharedUserLabel which says "The label must be set as a reference to
a string resource; it cannot be a raw string." and also set my sharedUserId as a
@string value.  However it turns out that the sharedUserId must be a raw string (the
opposite of sharedUserLabel).

The problem is that my already released free application has the sharedUserId set to
a value which didn't work.  I changed it to a raw string which now works to share the
database with the paid version.  However I posted my update of the free application
with the sharedUserId set to the new raw string value to Android Market without
realizing that the application would no longer be able to access its own database.
When people upgraded to the new version, it would crash as soon as it tried to open
its database.

I've run into this issue as well, was hoping that this might be moved out of the unreproducible state as I can't
add a sharedUserId to existing applications now.

I confirm this is still a problem on 2.1.

And it is easy to reproduce. I can provide a sample application demonstrating the
problem. Let me know if you need it.

And this is defect, not enhancement: developer doesn't expect that adding
sharedUserId to an application would forbid this application from accessing *its* data.