— this is interesting (and a terrific question!) I am going to try out the sequence of actions on my local app and see what my behavior is. If you have your code on GitHub let me know and I can build that version and see as well. So one thing that would be interesting to see is what the persisted ShareAction history is, and understand how it changes based on various actions you’ve shown above. See http://developer.android.com/guide/topics/ui/actionbar.html#ActionProvider
— there is a file (name provided by the DEFAULT_SHARE_HISTORY_FILE_NAME attribute) which stores the history of share actions, which is effectively what the SAP uses when reordering that list. I’m curious to see what the values in that are, after each action you outline. It should default to “share_history.xml” (though you can change it). If for any reason that is null, then the history does not get persisted across sessions I believe. The bottom line is that the ShareActionProvider uses the contents of this file to recreate the order in the menu, so somewhere something is not being written or read correctly from it. That’s my guess. If you find out differently, do post back here so I can update my FAQ as well.