Closed shubhamsinghshubham777 closed 1 year ago
hi!
when after pod install
you see that generated swift file shows in pods dir as here
you should not use pod install
anymore and deletion of geenrated files after gradle sync not affect your xcode. when you build app in xcode - framework will be automatically compiled and kswift code will be generated too, so all will be compiled successful.
i agree that integration flow now is complicated, but at now i not see some better way yet
Understood. Thanks for the response @Alex009 Closing this issue for now ✅
Hi here! First of all I want to thank the team who made this plugin possible, it's really useful 🌟
Now, I'm not sure if this is an issue of the plugin or gradle itself (or maybe I'm not setting up the plugin correctly) but whenever I make some updates to the
build.gradle
of theshared
module (where I have set up kswift as well) and click on theSync now
button (or even just restart IntelliJ IDEA and it automatically syncs gradle), it deletes the existingshared/build/cocoapods/framework/sharedSwift
folder that won't be generated until I do the following:Starting point: After gradle sync, the
sharedSwift
folder is no longer presentStep 1: Go to XCode and run the app until the build fails due to
sharedSwift
not being available anymoreStep 2: Come back to IntellJ IDEA, open the terminal, ensure that the
sharedSwift
folder is generated now and then runpod install
in its terminalStep 3: Go back to XCode, and from the popup, select
Read from disk
to make sure XCode reads the newly generated filesStep 4: Let
Step 3
finish its build completely and then the apprun/build
would finally succeedThis becomes quite tedious while developing 😅 Therefore I want to ask if there's a way to retain the previously generated files inside the
build
folder every time we sync gradle (or manually allow the generation of these generated files)?