Add workaround for useFrameworks:static

[enotniy]

Add fix for expo ios settings

"expo-build-properties",
  {
    "ios": {
      "useFrameworks": "static"
    }
  }

[Copilot]

Pull request overview

This PR adds a workaround for use_frameworks! :linkage => :static in iOS Podfile modifications. The change ensures that when a new target is inserted into the Podfile, any existing use_frameworks! directive is also included within that target block.

• Adds detection of existing use_frameworks! directives in the Podfile
• Includes the frameworks directive inside newly created target blocks
• Maintains compatibility with different use_frameworks! configurations

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The use_frameworks! directive is being detected globally but should only be included if it exists within the main target scope or at the root level, not within other targets. This could incorrectly duplicate a use_frameworks! directive that belongs to a different target.

Suggested change

	const frameworksMatch = podfile.match(USE_FRAMEWORKS_REGEX);
	const mainTargetEndIdx = podfile.indexOf("\nend", headerIdx);
	const searchEndIdx = mainTargetEndIdx === -1 ? podfile.length : mainTargetEndIdx;
	const frameworksMatch = podfile.slice(0, searchEndIdx).match(USE_FRAMEWORKS_REGEX);

[Copilot]

Unnecessary blank line added at end of file. Remove this trailing newline to maintain consistency.

Suggested change