@jon.zoom Can you show us how is the log we’re looking for supposed to look like?
Also I’ve build a mini app that just logs in into zoom and enables logs. This app also generates no log. Tried with different versions of the SDK. How can I shared it with you so you can tell me what am I missing?
In addition to enabling logging, it is important to note that the logFileSize must be set. This was being done in the snippet provided earlier, but I just wanted to make sure that part was clear.
Since this appears to be something specific to your project and/or dev environment, it will be difficult for me to be of any assistance in tracking down the cause since it does not appear to be an issue with SDK usage. If you are able to figure this out and provide logs or can narrow it down to an issue with the SDK itself, I will be happy to help.
@jon.zoom I created a sample project. This is the entire code. No logs are being created. Please point out the place where we incorrectly enable the logs:
I’m a little stumped on why we’re seeing such different results. If you are enabling logging through the method you have posted in this thread, it should be working.
Would it be possible for you to send your project to us at developersupport@zoom.us so that we can investigate further?
Where exactly did you find these logs? Since the test app is sandboxed, we were able to find the log in Containers for sandboxed apps.
~/Library/Containers//Data/Library/Logs/ rather than in the location you mentioned previously. Can you share the location and content of your folder? Here’s what I got
Yes, that does appear to be the correct files! Can you please send those over when you have a chance so that we can investigate the behavior you are seeing?
Hi @tmiskiew, thanks for the additional information.
I know that this issue has been ongoing for a while, but we still have not been able to reproduce this across many different environments internally.
Is it possible that you have anything out of the ordinary on your network (e.g. debug proxy, VPN, etc.)? If not, we’re unfortunately headed back to the drawing board on how to make progress on this.
Noted. I don’t have any updates on this for you just yet, but we are doing our best to figure out what could be causing these issues. Please bear with us as we investigate, as the inability to reproduce on our end may cause longer delays than usual.
Regardless, I will let you know as soon as we have any updates or if we need additional information in the future.
I don’t think that will be necessary. At this point, we fully understand the issue and you have done a great job of outlining the impact it has in your application. It’s just a matter of identifying what could be causing this which is preventing us from reproducing.
If I or anyone else on the team can think of something, I will absolutely reach out.