Hey everyone! This will likely come off as a "noobish" question, especially for someone who's on his 5th attempt at cracking the App Store! My question is the following: When you add new plugins and new files, you evidently have to recompile on Xcode. This involves downloading the newest source code. Now, which of the 2 is the preferred method of proceeding... 1) You drag and drop the new plugins/features from your new Xcode project to your previous Xcode project (I assume this would also mean replacing the Configuration file?) OR 2) The reverse - drag all your existing content into the new Xcode project, which evidently involves matching the build and target settings as well. Personally, I've been doing option #2 just to be safe; however, I feel like option #1 is the winner. Any clarification would be greatly appreciated as I'm trying to "do it right" this 5th and hopefully final time around. ;) Thanks again! Nicholas

I always do option 2, seems cleaner to me.

Thanks, that's pretty much the same reason I've been doing it. I guess I was just wondering if one is less complicated than the others/if one is more efficient in time compared to the other. Thanks again! Nicholas

I use option 1, if it's just a new plugin. Download the source code and just drag the new plugin into xcode. I use this method because what if you already made aditions to your code like push notifications or some other code. The you would loose all of that custom work. The plugin is already in the control panel on buzz touch so just adding it to the xcode project is enough. (recompile of course!)

ps. For plugins all you need to drag is the plgin folder.

I also added some code implementing a print function for my PDF files. I suppose I would be better off with option #1 in that case? I'm planning on going through with method #1 tomorrow and give it a shot. By the way, besides the plugins, do I have to drag anything else? For example, configuration files, JSON data, anything like that or do I simply need to drag the plugin files and recompile for the final product!? Thanks again!

In order that the app reviewer doesn't see the refresh on startup, I copy over the latest config.txt file into my project in xcode when I build the final archive and upload to apple, then I don't touch the app control panel until the app is approved (or not in my case).

Method #1 for sure. Once you start adding frameworks, adjusting build settings and modifying the source code, you'll loose all that if you start a new project. Adding new plug-in files to the source is nothing more than creating a new subfolder folder in the BT_plugins folder. You can download a 'new' source and copy those new files to the old project. This way you see the intended structure of the plugin too (if it has some subfolders....) and finally keep in mind it does depend on when you originally downloaded the source code. there are some little bugs and tweeks they add to the BT Core files that we don't always see unless David posts about it.

Thanks for the feedback, guys! Method #1 should definitely do the trick based on the explanations given above. Will get on it later today - I don't think I should run into any particular issues with the BT Core Files since it will be roughly 2 weeks between Source Code downloads, of course, unless there have been any bugs or tweeks during that time that I'm not aware of ;) Thanks again! Nicholas