Posts

Post not yet marked as solved
1 Replies
0 Views
MessageComposeResultFailed will be fired when the user’s attempt to save or send the message was unsuccessful. You can refer documentation for more details. https://developer.apple.com/library/prerelease/ios/documentation/MessageUI/Reference/MFMessageComposeViewController_class/index.html#//apple_ref/c/tdef/MessageComposeResult It means maybe some internal system/OS issue and in some cases message sending is blocked by the network provider. In general this delegate is very rare to get caught firing. Also The delegate method can report MessageComposeResultSent even if all your app did was give the message to the system to send. It's not a guarantee that it actually sent the message.
Post marked as solved
2 Replies
0 Views
Disable all actions by UITextField subclass. import UIKit class CustomTextField: UITextField { override func canPerformAction(_ action: Selector, withSender sender: Any?) -> Bool { return false } }
Post marked as solved
3 Replies
0 Views
Thanks Mark Eaton @meaton, I have the following queries on these A) Does SSL pinning using NSIncludesSubdomains support multiple subdomains like wang.greenhub.example.org by any other way, because as per official documents it doesn’t apply to the subdomains advanced.math.example.com or ancient.history.example.com because those subdomains have two additional path components. Is Apple planning to work on this in future or some way is there to make NSIncludesSubdomains work with multiple subdomains? I tried using wildcard *.example.org but it does not seem to work B) And also in such case of multiple subdomains do we need to move back for traditional certificate pinning but AFAIK this method is dependent on certificate expiry date i.e on each certificate expiry we must upload a new build to AppStore with new certificate. Please kindly reply Thanks and regards, Alex