feat(Instagram): Support app version 378.0.0.52.68 and add bypass check signature

[hoo-dles]

So the fix for the ads fingerprint is straightforward. The method is still there, but one of the string matches is now gone. Fingerprint is still unique with just the remaining string.

Since v371+, any modified/resigned app crashes on startup during splash screen, so there must be some sort of signature check. The class I'm patching has a string reference of "IgSecureContext", so makes sense.

Instagram's code is highly obfuscated, but the instafel standalone project had a fix that I tested out. It stopped the app from crashing, so I wrote a revanced patch that doesn't rely on obfuscated class/method names.

I need help testing because I don't use IG, and Meta's auto-detection tools really do not like my burner account.

[hoo-dles]

Related: #4891 #4723 #4584

[cyberboh]

Well, I built this PR and patched IG v378, all patches applied successfully. After testing, I can login into the app and ads disappear on home feeds. So, basically all patches work as expected.

My bug #4584 is fixed by this PR.
Also, possibly fixes #3651 and I tested with this issue, also fixed by Bypass signature patch #4317 as discussed here https://github.com/orgs/ReVanced/discussions/1117

For this issue #55 I thought fixed also, but on my device there is no share to Story. So, new additional patch is needed.

[cyberboh]

@hoo-dles Maybe be need to refactor the Bypass signature in order to support IG version latest available. So, no need to constrains to 378. But for initial, the patch is super. Kudos. 🚀

[Karthik-Subbu]

There was a version constraint to 350.0.0.43.93 as the links couldn't open in the app instead of browser. Is it still valid?

[cyberboh]

There was a version constraint to 350.0.0.43.93 as the links couldn't open in the app instead of browser. Is it still valid?

I tested 378.0.0.52.68 with this PR, any IG links can be opened directly to app. 👍

[Karthik-Subbu]

Thanks much @hoo-dles and @cyberboh

[hoo-dles]

@oSumAtrIX most of the review comments are a consequence of taking the patching logic from a separate project (noted in the code and initial PR comment). I am making my best guess at the changes in logic from working backwards. This section of the code is obfuscated (which is why I don't have proper class names either).

The original patch does not conform to revanced best practices, as the author searches for classes/methods by obfuscated name (eg. X.A00.A01()). I did my best to back trace to identifiable fingerprints.

[hoo-dles]

The original patch essentially makes the following change:

// class X.1he

public static final void A01(Context context, Intent intent) {
    // Take A00.A0x() from A02() and replace in A01()

    // A00.A07().A05(context, intent);
    A00.A08().A05(context, intent);
}

public static final void A02(Context context, Intent intent) {
    A00.A08().A0C(context, intent);
}

This is where X.1he.A01() is called:

public final class LauncherActivity extends IgFragmentActivity implements InterfaceC47421dy {
    public UserSession A00;

    private final void A00(Intent intent, Bundle bundle) {
        Intent intent2 = new Intent();
        intent2.setClassName(this, "com.instagram.mainactivity.InstagramMainActivity");
        intent2.setData(intent.getData());
        intent2.setFlags(67108864);
        intent2.putExtras(intent);
        boolean z = C31023Brl.A05;
        if (bundle != null) {
            intent2.putExtras(bundle);
            intent2.putExtra("redirect_from_launcher_activity", true);
        }
        C49701he.A01(this, intent2); // <---- Here
        finish();
    }

...

[cyberboh]

@hoo-dles Quick test IG 379.0.0.41.80-build-378313536-arm64-v8a-nodpi patched successfully. Installed on top of 378.0.0.52.68-build-378213511 so far no issue.

[Figim]

There is a new project that is updated frequently. You get automatic updates within the app. https://github.com/mamiiblt/instafel

[cyberboh]

@hoo-dles 379.1.0.43.80 build 378313923 arm64-v8a (nodpi) patched successfully.

[LisoUseInAIKyrios]

@hoo-dles is this ready to merge?

[hoo-dles]

@hoo-dles is this ready to merge?

@LisoUseInAIKyrios ready on my end