If you are using both of these plugins and also WP_Cache then when you upgrade WPTouch you will get the following misleading message.
WPtouch: WordFence was recently disabled, but is still affecting your website and caching pages. Please reactivate the plugin, disable page caching, then deactivate the plugin again to correct this issue. Fixing this issue prevents cached desktop pages being served to mobile devices and vice-versa. Once fixed, this message will be dismissed automatically. Until fixed, WPtouch will not be shown to mobile visitors, and cannot be previewed.
To get rid of this message you need to go into the "Performance Setup" tab within the WordFence settings in the back end. Temporarily enable the caching option there and then disable it again.
The message is totally misleading as to what you need to enable and then disable again as it is not WordFence that is disabled but WordFence caching (which is disabled anyway as a completely different caching plugin is being used).
The message is a bit more useful when you are using a different caching plugin. For example if you are using WP_Super_Cache then the message you get is:
WPtouch: WP Super Cache needs to be configured to work correctly with WPtouch. Fixing this issue prevents cached desktop pages being served to mobile devices and vice-versa. Once fixed, this message will be dismissed automatically. Until fixed, WPtouch will not be shown to mobile visitors, and cannot be previewed. To fix the issue, follow our step-by-step setup guide on support.wptouch.com
If you get this variant of the message then go into the WP Super Cache settings and then in the Advanced tab deselect "Mobile Device Support" and click "Update Status". Next scroll down to the "Rejected User Agents" area. Paste the entire list of mobile user agents found below and click "Save UA Strings".
Now go to thee “Contents” tab, click “Delete Expired” and “Delete Cached” to delete pages that were likely cached before adding the new list of rejected user agents.
If you get a different variant of this message because you are using a different caching plugin then look at support.wptouch.com to see if there are instructions there for fixing your particular caching module.