Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Return nil if it's compiled as a dynamic framework

Open
#36 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
ios, objective-c
Domain
mobile

Research direction

Start by reproducing FDStackView initialization in the Objective-C iOS 8 project described, comparing a normal CocoaPods integration with a Podfile using use_frameworks!. Trace the initialization path when the library is built as a dynamic framework; done means FDStackView no longer returns nil without manually adding its code to the application.

Written by the indexing model from the issue text.

Description

I use CocoaPods to manage third-party libraries.

There are some reasons causes I had to add use_frameworks! to the Podfile, so all of the libraries are compiled as a dynamic framework.

But I found that if FDStackView is compiled into a dynamic framework, it will return nil when it's initialized.

Is there any workaround? I don't want to add the code to my project manually.

FYI:
Objective-C-based project.
iOS 8.

Dominant language
Objective-C
Stars
2.5k
Forks
310
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from forkingdog/FDStackView

All issues in forkingdog/FDStackView

Similar issues

More Objective-C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.