Rob, I apologize for late response as I was busy working on another project. I could not “see” or “find” any error on device’s console log using “adb logcat” command. Because logs are running so fast, I can not find any error related to the problem.
Is there any easier way to be able to see the logs?
It is like searching a for a needle in a haystack, but unfortunately no. If you’re on a Mac, and you don’t close the dialog box after building, we do direct the android console log to the Corona console log. If you’re on Windows, there isn’t much that you can do other than scroll back and look.
Rob, the problem is that I can not see the logs on iOS devices lately. I don’t know when it happened but I think it’s been more than a month. After the debug build finishes, I don’t see any logs.
Rob, the device is iPhone 6S Plus. I’ll try with Xcode and see if it shows anything. However, the actual post is about sharing on Android. I’ll try on iOS too to see if it works.
Though, on Android I don’t see anything related to the whatsapp sharing on the Corona logs while the device is connected.
@bamazy, I’m quite very confused. This post started out as issues with the Social plugin on Android. You should not be using it on iOS. The iOS version of this was for iOS 6/7 and has been replaced by the Activity plugin starting with iOS 8. I’m not sure why you brought up not being able to see the console log from the device on iOS. If this is a separate issue, you should start another thread. Let’s focus this thread on the Android issue. A capture of your “adb logcat” would be much more usable. The point I’m making is if you’re using Corona on a Mac to build (even for Android), we should redirect the “adb logcat” output and try to filter out messages relative to Corona which can be easier than dealing with the full “adb logcat” dump.
Corona (or any one else) cannot autostart an app on iOS. We can on Android. This is an iOS limitation.