Does Apple's rejection of apps with hot code push impact apps with Optimizely SDK
Apple has started rejecting apps that make changes after the app is live in the app store. From the apple dev forums  and discussion on Hacker News it looks like it was targeted at apps that use the rollout.io SDK that allows hot code push.
The forum post says
This includes any code which passes arbitrary parameters to dynamic methods such as dlopen(), dlsym(), respondsToSelector:, performSelector:, method_exchangeImplementations(), and running remote scripts in order to change app behavior or call SPI, based on the contents of the downloaded script
Does the Optimizely SDK use any of these techniques for live variables or the visual editor?
Optimizely ought not be impacted by this change in policy. Optimizely does not actually *change* the app once it is published. It merely activates or de-activates certain features that are already embedded in the Mobile App. There is no "code push" involved in running an experiment in the app.
(But, "ought not" is not the same as "will not"... so I defer to the Optimizely App team for verification)
Analytics and Testing Guru
With live variables and code blocks, Optimizely SDK merely activates and deactivates the content but when the visual editor is used, it swizzles and changes the app content after it is published. I was curious if that was going to be a problem.