Since the activity-alias is backed by the same code as the original
activity definition, they should both have an identical encryption
awareness. This fixes a bug where we accidentally dropped that value.
Bug:
26731340
Change-Id: I6ad615332df7d16542893a49e6997c88fc24334b
info.maxRecents = target.info.maxRecents;
info.layout = target.info.layout;
info.resizeMode = target.info.resizeMode;
+ info.encryptionAware = target.info.encryptionAware;
Activity a = new Activity(mParseActivityAliasArgs, info);
if (outError[0] != null) {