-
Notifications
You must be signed in to change notification settings - Fork 268
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can we use CFBundleExecutable instead of CFBundleName? #359
Comments
That was for swift name-spacing. Does it work with CFBundleExecutable? |
Yes, we tried and it worked. But we are using pod for our CI, so it is Thanks On Thursday, May 28, 2015, Jasper Blues notifications@github.com wrote:
|
Ok. Please paste the update method from |
Just change NSString *defaultModuleName = [[NSBundle mainBundle] objectForInfoDictionaryKey:@"CFBundleName"]; to NSString *defaultModuleName = [[NSBundle mainBundle] objectForInfoDictionaryKey:@"CFBundleExecutable"]; |
Done. You can now try this with: pod 'Typhoon', :head |
It is working now. thanks. |
Thank you :) |
We encounter a problem with changing app name when we are using Typhoon framework.
The problem is in TyphoonIntrospectionUtils.m, for function "Class TyphoonClassFromString(NSString *className)"
NSString *defaultModuleName = [[NSBundle mainBundle] objectForInfoDictionaryKey:@"CFBundleName"];
So if we change the BundleName in Info.plist to a different name from the project name, the Typhoon won't work any more.
Can we use CFBundleExecutable or something else instead? So that we can easily change our app name.
Thanks a lot.
The text was updated successfully, but these errors were encountered: