The IDFV testing tool app allows AppsFlyer to identify your device as a testing device by preserving your app's IDFV (Identifier For Vendor) across consecutive installations.
If you repeatedly delete and reinstall your app on a device for testing purposes, the install events will not be recorded unless you register the device identifier as belonging to a testing device in AppsFlyer.
However, when the identifier type is IDFV (Identifier For Vendor) and the tested app is the only app on the device associated with the vendor, the IDFV value will be replaced with a new value each time the app is deleted and reinstalled. Consequently, AppsFlyer will not recognize the device as a testing device because the IDFV value used for device registration was replaced by a different value.
To address this, the IDFV testing tool app, when installed on the testing device, emulates belonging to the vendor of the tested app. As a result, the registered IDFV value remains unchanged even when the tested app is deleted and reinstalled.
To enable the app to emulate belonging to the same vendor as the tested app, it has to be signed with the vendor's IDFV value before it is compiled and installed on the tested device.
Clone the IDFV testing tool app repository to your local machine.
Open Xcode and select the project in the Project Navigator.
Under TARGETS select the target for your IDFV testing tool app.
Expand the Signing section.
In Bundle Identifier, enter an identifier with an identical prefix to the identifier of the app you are testing.
For example, if your tested app's Bundle Identifier is
com.MyCompany.apps.myapp, you should change the IDFV testing tool Bundle Identifier (
Build and install the IDFV testing tool on the device. The new app receives the same IDFV as your tested app.
Launch the IDFV testing tool app. The IDFV number is displayed in the app. You can use the IDFV when manually regisering the device as a testing device.
최신 데이터 4개월 전