Segment deprecated these options: Deprecated Optionĭeprecated in favor of the enrichment plugin that adds the default data to the event payloads.ĭeprecated in favor of a plugin that provides the same functionality. Set this to false if you want to customize the initialization of the Segment Destination, such as, add destination middleware. The analytics client automatically adds the Segment Destination. Segment changed these config options: Before add ( plugin : amplitudeDestination ) Update your config options add ( plugin : customizeAmplitudeTrackCalls ()) // add amplitude to analytics instance.

You can use 'Swift + Objective-C' as of now to make your app running smoothly and also giving updates regularly rather than waiting for the months to convert it completely.Class customizeAllTrackCalls : EventPlugin // create an instance of the Amplitude plugin let amplitudeDestination = AmplitudeDestination () // add our enrichment plugin to amplitude amplitudeDestination.

You may end-up having clean code under proper structure.You may find some unusual code or libraries lying around.Andreas Oetjen Suggestion: You might start by separating the class hierarchy, and convert one 'subtree' after the other.Besides, you can also build modules from scratch in the form of smaller projects and then just drag and drop in Objective-C project.Once you are done with smaller ones, slowly start picking up big modules also you may find open source Swift libraries which are in Objective-C in your project.Reference: How can I import Swift code to Objective-C? From your project, first of all start picking up smaller modules which don't affect app in any way and see that the 'Swift' file works well with Objective-C (Your old code).Rather than start converting complete project, adapt modular way.Pick the latest version of Swift (i.e.So what I suggest you to go via following way: Converting a full objective-C app to Swift by Naveen Saraswat Sodio Technologies Medium Sign In 500 Apologies, but something went wrong on our end.

The biggest problem is that Swift is still evolving and probably next year we might see 'Swift 5.0'. Your approach of converting Objective-C to Swift is wrong! Apple also took time to adopt Swift completely in their frameworks and the news is in 2018, 85% of the frameworks are converted to Swift, so the point is they has also taken nearly 3 years to get it done!

Objective c to swift migration