But isn't the newznab support the only thing that's been added? If 0.4.17 is ok with apple and was approved and still available on the app store, why would you need to remove features that have been approved time and time again in the past? It's unlikely, but maybe it is the newznab support that has been 'flagged' in the rejected 0.4.18 (there are currently approved apps with newznab support available on the app store) I really hope not, but this app needs newznab support and I'd hate to sacrifice the good 'ol raw search engines that have been hard coded in for as long as I remember.
After you submit a version without hardcoded providers could you tell us If it would be possible to have the app accept urls to provider configs (adding providers via a URL that tells mynzb how to handle the provider.) You could then document the process of creating these configs for anyone to create for any provider. Just an idea.
That sounds good, I remember seeing another sab remote app that does something similar. This would sort of future-proof the app so you could update providers without having to re-submit to apple, I like it!
Yeah, well, it's a feature of my app... Been there since the beginning. Wouldn't help at that point for myNZB because the app has already been flagged: anything "dynamic" will be a problem for Apple now...
App looks and works mostly great but it closes for some reason pretty randomly. Is there a way for me to send you the log? I'm running iP5 with iOS 6.1.2. I can jailbreak it if you need.
To bad, would rather see a quick update for iOS7 as it's unusable for me now since the "popup" screens where you select a server or a download category seem to be broken now.
