Recently we noticed that some concerns are raised about the MTGInvocationBoxing Class related functions from the Mintegral SDK, and we would like to explain everything in detail in this article.
MTGInvocationBoxing Class was added to the Mintegral SDK version 6.2.0 updated on April 17, 2020, to assist with Mintegral’s multiple video ad functionality. As this technology has few precedents in the industry and is very complex and difficult to manage, the introduction of MTGInvocationBoxing Class was intended to fix possible bugs in the process of H5 template functionality improvements and provide a good developer experience, but this function has not actually been used.
MTGInvocationBoxing Class can only call classes that have been written in the Mintegral SDK, which causes no harm to developers, and Mintegral technical team has restricted the use of this class. In order to avoid concerns about “remote code control” as mentioned in the email, we have provided a screenshot of the backend code, please see below.
MTGInvocationBoxing is the class used by MTGSDK to fix potential online issues with the H5 template. It can send messages to specified objects, and it can only act on objects marked as Ref.
“rv/show/adrequest”: the object used to display the rewardVideo ad
“rewardvideo/rewardunitsetting”: the “MTGRewardUniting” object used when displaying rewardVideo
“videoViewController”: the “MTGViewController” object used to present a video player view
“templatePlayerView”: the player when playing the video
“templateWebView” : the WKWebView object used when playing the ad
“templateCommonJS/load”: the “MTGCommonJS” object used to interact with a WKWebView while requesting an ad
“templateCommonJS/show”: the “MTGCommonJS” object used to interact with a WKWebView while displaying the video ad
“storeKitVC/template4”: the “MTGCommonJS” object used when the user clicks on the storekit that appears after displaying the ad
“iv/adManagerComposite”: the “MTGAdmanagerComposite” object which is used to request an ad
“iv/bid/adManagerComposite”: “MTGAdmanagerComposite” object which is used to request a bid for an ad
“minicardView”: the object is used to show a minicard view when showing the ad
“endcardView”: the object is used to show an endcard view when showing the ad
“playableView”: the object is used to show a playable view when showing the ad
The following shows how to maintain the specified object.
The code in the screenshot above shows the function used to control ad requests, clicks, impressions, and other SDK-related functionality. Any possible functionality outside this range will result in an error, making it impossible for this to cause any issues to developers.
Due to a recent malicious attack on the Mintegral SDK by competitors, the Mintegral technical team assessed that there is a possibility that competitors may use part of the code to maliciously trigger Apple’s audit mechanism. Therefore, the Mintegral team has taken the initiative to delete it from the open-source version 6.6.0 and newer in order to avoid malicious interpretations. It has been confirmed that MTGInvocationBoxing Class only exists in versions 6.2.0 – 6.5.0, so no such problems should exist in versions before 6.2.0 and versions after 6.5.0.
Now, developers who updated to version 6.6.0 and above have already been approved by Apple App Store. Developers who have not updated to version 6.6.0 and above can download it from the Mintegral official website. The latest version is 6.6.3 and it has been updated here: https://github.com/Mintegral-official/MintegralAdSDK-iOS-new. If you are accessing Mintegral through mediation platforms, please send an email to email@example.com and the Mintegral operations team will help you update to the latest version.