callstack_repack-Swift.h file not found

[jefmoraes]

I'm having a failure when executing the application build in Xcode 15, I installed the pods correctly but I don't know why this happens, I have another project and everything happened correctly there

I discovered that the file that should be generated is not being generated by Xcode in DerivedSources the generated file is callstack_repack _vers.c when it should be callstack_repack-Swift.h

[sternlucas]

Same problem here

[jbroma]

@jefmoraes @sternlucas can you provide me with your cocoapods version being used in the projects?

[jbroma]

@jefmoraes @sternlucas I'm not able to reproduce this issue on a fresh react-native project created using CLI, can you provide even more details about your environment? Here is what i tried it on:

1. System: Sonoma 14.1
2. Xcode: 15.2
3. Ruby: 2.7.6
4. Cocoapods: 14.3
5. Node: 20.11.1

[mlakmal]

@jbroma seeing same issue when i tried to integrate re.pack to existing application

Sonomae 14.3.1 XCode 15.2 Ruby 2.7.6 cocoapods 1.11.2 node 16.14.2

react-native 0.68.6 @callstack/repack ^3.7.0

i tried setting up superapp example and it worked fine with above core deps

[jbroma]

@mlakmal did you run pod install after adding repack?

[mlakmal]

@mlakmal did you run pod install after adding repack?

yes i did. it installed the Pods. below is the screenshot in xcode with pod files.

[jefmoraes]

here the problem was related to the use of use_frameworks! :linkage => :static, just add the code bellow it to the podfile and run pod install. This way, in build phases in the callstack-repack pod you will notice that the Copy generated compatibility header file will be generated, it is responsible for guiding the import paths.

pre_install do |installer|
   installer.pod_targets.each do |pod|
     if pod.name.eql?('callstack-repack')
       def pod.build_type
         Pod::BuildType.static_library
       end
     end
   end
 end 

After

Before

[jbroma]

Looks like it's related to #390

[mlakmal]

i do see use_frameworks! in our podfile let me give it a shot at above fix and let yall know...

[mlakmal]

that workaround did not resolve the issue for me.

fyi: point to note is that i had to manually link the callstack-repack in Podfile. wonder if thats causing the issue...

[github-actions[bot]]

This issue has been marked as stale because it has been inactive for 30 days. Please update this issue or it will be automatically closed in 14 days.

[jbroma]

@mlakmal did you manage to resolve this?

[lakmal-gentem]

Yes I am not sure what combination actually worked. I did all below and it's solved now. Tnx

• Add callstack as static in profile
• Add manual link in profile for callstack. Yarn didn't auto link...
• Re-setup ruby env

[jbroma]

@mlakmal @jefmoraes Potential fix for this issue has been merged, it will be included in 4.0.0-rc.2 which should be available today 🎉

If there is an option for you to test whether this fixes the problem without adjusting Podfile in your projects, please do and let me know if that helped 🙏

[mlakmal]

@mlakmal @jefmoraes Potential fix for this issue has been merged, it will be included in 4.0.0-rc.2 which should be available today 🎉

If there is an option for you to test whether this fixes the problem without adjusting Podfile in your projects, please do and let me know if that helped 🙏

thanks for the fix. will try it later next week and get back to you!

[HebertGB]

@mlakmal @jefmoraes Potential fix for this issue has been merged, it will be included in 4.0.0-rc.2 which should be available today 🎉

If there is an option for you to test whether this fixes the problem without adjusting Podfile in your projects, please do and let me know if that helped 🙏

I confirm that the repack upgrade from 3.7.0 to 4.0.0-rc-2 resolved this issue without need to add "pre_install ..." to Podfile.

[ichina]

@mlakmal @jefmoraes Potential fix for this issue has been merged, it will be included in 4.0.0-rc.2 which should be available today 🎉

If there is an option for you to test whether this fixes the problem without adjusting Podfile in your projects, please do and let me know if that helped 🙏

i confirm that the issue is fixed in 4.0.0-rc-2

[mlakmal]

@mlakmal @jefmoraes Potential fix for this issue has been merged, it will be included in 4.0.0-rc.2 which should be available today 🎉 If there is an option for you to test whether this fixes the problem without adjusting Podfile in your projects, please do and let me know if that helped 🙏

thanks for the fix. will try it later next week and get back to you!

yes this is working on ours as well!