[TIMOB-26391](7_4_X) Improve proxy protection logic

[janvennemann]

JIRA: https://jira.appcelerator.org/browse/TIMOB-26391

Optional Description:
Using the existing protect/unprotect methods caused unwanted side effects. This introduces two similar methods for the sole purpose of safeguarding the JS object during our proxy creation flow.

[vijaysingh-axway]

Both apps are working fine at my end.

[vijaysingh-axway]

Two methods which you have introduced-
-(void)applyGarbageCollectionSafeguard
-(void)removeGarbageCollectionSafeguard
Is similar to

• (void)protectJsobject
• (void)unprotectJsobject

Only difference I can see is updating location of bool ‘gcSafeguarded’ and ‘protecting’ in theses functions. Is bool value updating location is cause of some issue?

[janvennemann]

Both methods basically do the same, yes. The reason i introduced them is because the are operating on another flag. We use protectJsobject/unprotectJsobject in various other places and calling in https://github.com/appcelerator/titanium_mobile/pull/10370/files#diff-c486238fd67efff24b4b0a311e95c358L230 was causing the issues. With this fix only the initial protection during the proxy creation will be removed and not any protect calls which are required later during runtime.

[vijaysingh-axway]

CR passed.

[build]

	Messages
📖	💾 Here's the generated SDK zipfile.

Generated by 🚫 dangerJS