Upgrade the iOS SDK from 2.5.12 to 2.5.13

Integration via pods

  1. Update your pod file: deployment target remains the same as for 2.5.10 (it should be 9.0) and pod version should be changed from '2.5.12' to '2.5.13'.

Manual integration

  1. Manual integration stays the same as for 2.5.12. All libraries remain the same

Changes

You can use the +updateConsent: method to provide the GDPR user consent for ad networks in Appodeal SDK anywhere of your application. Appodeal SDK don't keep the GDPR user consent between session, that means you should provide consent every time, otherwise, Appodeal SDK uses default or server value. By default consent value is true.

Upgrade the iOS SDK from 2.5.11 to 2.5.12

Integration via pods

  1. Update your pod file: deployment target remains the same as for 2.5.11 (it should be 9.0) and pod version should be changed from '2.5.12' to '2.5.11'.
  2. Several subspecs was renamed:

    pod 'Appodeal/AppodealAdExchangeAdapter', '2.5.12' 
    pod 'Appodeal/IronSourceAdapter', '2.5.12'

Manual integration

  1. Manual integration stays the same as for 2.5.1. All libraries remain the same

Upgrade the iOS SDK from 2.5.10 to 2.5.11

Integration via pods

  1. Update your pod file: deployment target remains the same as for 2.5.10 (it should be 9.0) and pod version should be changed from '2.5.10' to '2.5.11'.

Manual integration

  1. Manual integration stays the same as for 2.5.10. All libraries remain the same

Upgrade the iOS SDK from 2.5.9 to 2.5.10

Integration via pods

  1. Update your pod file: deployment target remains the same as for 2.5.9 (it should be 9.0) and pod version should be changed from '2.5.9' to '2.5.10'.

Manual integration

  1. Manual integration stays the same as for 2.5.9. All libraries remain the same


Upgrade the iOS SDK from 2.5.8 to 2.5.9

Integration via pods

  1. Update your pod file: deployment target remains the same as for 2.5.5 (it should be 9.0) and pod version should be changed from '2.5.8' to '2.5.9'.
  2. If you use only some parts of Appodeal SDK (ad types), pod file updating will be the same. For example: from "pod 'Appodeal/Banner', '2.5.8' " to "pod 'Appodeal/Banner', '2.5.9'" and deployment target stays the same as for 2.5.8 (it should be 9.0)

Manual integration

  1. Manual integration stays the same as for 2.5.8. All libraries remain the same

Changes

  1. Add your GADApplicationIdentifier into info.plist file

<key>GADApplicationIdentifier</key>
<string>ca-app-pub-3940256099942544~1458002511</string>

Upgrade the iOS SDK from 2.5.7 to 2.5.8

Integration via pods

  1. Update your pod file: deployment target remains the same as for 2.5.5 (it should be 9.0) and pod version should be changed from '2.5.7' to '2.5.8'.
  2. If you use only some parts of Appodeal SDK (ad types), pod file updating will be the same. For example: from "pod 'Appodeal/Banner', '2.5.7' " to "pod 'Appodeal/Banner', '2.5.8'" and deployment target stays the same as for 2.5.7 (it should be 9.0).
  3. FBAudienceNetwork 5.4.0 has FBSDKCoreKit as external dependency and will be installed when your update Appodeal SDK to 2.5.8

Manual integration

  1. Manual integration stays the same as for 2.5.7. All libraries remain the same

Upgrade the iOS SDK from 2.5.6 to 2.5.7

Integration via pods

  1. Update your pod file: deployment target remains the same as for 2.5.5 (it should be 9.0) and pod version should be changed from '2.5.6' to '2.5.67.
  2. If you use only some parts of Appodeal SDK (ad types), pod file updating will be the same. For example: from "pod 'Appodeal/Banner', '2.5.6' " to "pod 'Appodeal/Banner', '2.5.7'" and deployment target stays the same as for 2.5.6 (it should be 9.0).
  3. FBAudienceNetwork 5.4.0 has FBSDKCoreKit as external dependency and will be installed when your update Appodeal SDK to 2.5.7

Manual integration

  1. Manual integration stays the same as for 2.5.6. All libraries remain the same

Upgrade the iOS SDK from 2.5.5 to 2.5.6

Integration via pods

  1. Update your pod file: deployment target remains the same as for 2.5.5 (it should be 9.0) and pod version should be changed from '2.5.5' to '2.5.6'.
  2. If you use only some parts of Appodeal SDK (ad types), pod file updating will be the same. For example: from "pod 'Appodeal/Banner', '2.5.5' " to "pod 'Appodeal/Banner', '2.5.5'" and deployment target stays the same as for 2.5.5 (it should be 9.0).

Manual integration

  1. Manual integration stays the same as for 2.5.5. All libraries remain the same

Upgrade the iOS SDK from 2.5.4 to 2.5.5

Integration via pods

  1. Update your pod file: deployment target remains the same as for 2.5.4 (it should be 9.0) and pod version should be changed from '2.5.4-Beta' to '2.5.5'.
  2. If you use only some parts of Appodeal SDK (ad types), pod file updating will be the same. For example: from "pod 'Appodeal/Banner', '2.5.4-Beta' " to "pod 'Appodeal/Banner', '2.5.5' " and deployment target stays the same as for 2.5.4 (it should be 9.0).

Manual integration

  1. Manual integration stays the same as for 2.5.5. All libraries remain the same

Upgrade the iOS SDK from 2.5.3 to 2.5.4

Integration via pods

  1. Update your pod file: deployment target remains the same as for 2.5.2( it should be 9.0) and pod version should be changed from '2.5.3-Beta' to '2.5.4-Beta'.
  2. If you use only some parts of Appodeal SDK (ad types), pod file updating will be the same. For example: from "pod 'Appodeal/Banner', '2.5.3-Beta' " to "pod 'Appodeal/Banner', '2.5.4-Beta' " and deployment target stays the same as for 2.5.3 (it should be 9.0)

Manual integration

  1. Manual integration stays the same as for 2.5.3. All libraries remain the same
  2. Update rewarded video callback on reward. 

Upgrade the iOS SDK from 2.5.2 to 2.5.3

Integration via pods

  1. Update your pod file: deployment target remains the same as for 2.5.2( it should be 9.0) and pod version should be changed from '2.5.2-Beta' to '2.5.3-Beta'.
  2. If you use only some parts of Appodeal SDK (ad types), pod file updating will be the same. For example: from "pod 'Appodeal/Banner', '2.5.2-Beta' " to "pod 'Appodeal/Banner', '2.5.3-Beta' " and deployment target stays the same as for 2.5.2 (it should be 9.0).

Manual integration

Manual integration stays the same as for 2.5.2. All libraries remain the same.

Upgrade the iOS SDK from 2.5.0 to 2.5.2

Integration via pods

  1. Update your pod file: deployment target remains the same as for 2.5.0( it should be 9.0) and pod version should be changed from '2.5.0-Beta' to '2.5.2-Beta'.
  2. If you use only some parts of Appodeal SDK (ad types), pod file updating will be the same. For example: from "pod 'Appodeal/Banner', '2.5.0-Beta' " to "pod 'Appodeal/Banner', '2.5.2-Beta' " and deployment target stays the same as for 2.5.0 (it should be 9.0).

Manual integration

Manual integration stays the same as for 2.5.0. All libraries remain the same.

Upgrade the iOS SDK from 2.4.10 to 2.5.0 beta

Integration via pods

  1. Update your pod file: deployment target remains the same as for 2.4.10 ( it should be 9.0) and pod version should be changed from '2.4.10' to '2.5.0-Beta'.
  2. If you use only some parts of Appodeal SDK (ad types), pod file updating will be the same. For example: from "pod 'Appodeal/Banner', '2.4.10' " to "pod 'Appodeal/Banner', '2.5.0-Beta' " and deployment target stays the same as for 2.4.10 (it should be 9.0).

Manual integration

Manual integration stays the same as for 2.4.10. All libraries remain the same.