You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe 🙏
I recently integrated the InstantSearch SDK v7.26.1 and AlgoliaSearchClient SDK v8.19.0 in our iOS app in order to trigger several InstantSearch Insights events.
After I finished my integration debugging I was left with a verbose logging in my console that I cannot turn off. Every 30 seconds I get a log like this:
2024-03-06T14:37:01+0200 info Insights (B5UR3QDMCF) : [InstantSearchInsights] no pending event packages, skip flushing
2024-03-06T14:37:31+0200 info Insights (B5UR3QDMCF) : [InstantSearchInsights] no pending event packages, skip flushing
2024-03-06T14:38:01+0200 info Insights (B5UR3QDMCF) : [InstantSearchInsights] no pending event packages, skip flushing
2024-03-06T14:38:31+0200 info Insights (B5UR3QDMCF) : [InstantSearchInsights] no pending event packages, skip flushing
2024-03-06T14:39:01+0200 info Insights (B5UR3QDMCF) : [InstantSearchInsights] no pending event packages, skip flushing
2024-03-06T14:39:31+0200 info Insights (B5UR3QDMCF) : [InstantSearchInsights] no pending event packages, skip flushing
Is your feature request related to a problem? Please describe 🙏
I recently integrated the InstantSearch SDK v7.26.1 and AlgoliaSearchClient SDK v8.19.0 in our iOS app in order to trigger several InstantSearch Insights events.
After I finished my integration debugging I was left with a verbose logging in my console that I cannot turn off. Every 30 seconds I get a log like this:
I instantiate Insights with:
I tried this, but it had no effect:
This logging past the integration phase is unnecessary and pollutes the console, making it hard to see important logging.
Describe the solution you'd like 🤔*
Provide a way to turn of the logging, or better yet, make logging default to silent and only activate it when needed.
The text was updated successfully, but these errors were encountered: