Support the latest version 1.16.4-CL36651368 - 2024 10/8

[jadeeeeeeeee]

1.16.4-CL36651368 - 2024 10/8
Supports PC and mobile devices (iOS+Android), with more payment functions,
May I ask when we can release a plugin that is compatible with this SDK version? I am in a hurry to use it.
As far as I know, the FallGuys game has already been supported.

Thank you very much for your team's support

[arthur740212]

Hello, we are in the release process for 1.16.4 support currently, we could expect the release to be out within the next two weeks.

[jadeeeeeeeee]

Hello, we are in the release process for 1.16.4 support currently, we could expect the release to be out within the next two weeks.

We are in a hurry~
If there is a pre version that has not been released yet, you can give us one first,
I can develop it first, and then replace it when you officially release it.
Thank you.

[paulhazen]

Hi @jadeeeeeeeee, unfortunately that's not something we are able to do. I can tell you that we anticipate that the new release will happen this week - and I will update this thread when and if that estimation changes.

[jadeeeeeeeee]

Hi @jadeeeeeeeee, unfortunately that's not something we are able to do. I can tell you that we anticipate that the new release will happen this week - and I will update this thread when and if that estimation changes.

Thank you very much, I have been waiting.

[arthur740212]

Hello, while we are still working on the release, users are still able to preview the plugin by building a package from the development branch.
The current state of development does have 1.16.4 integrated, so if you would like to try it out, the plugin should function.
All you have to do is clone this repo, run it in Unity, and use Create Package in the Tools tab.
Let us know if you have any problems with the package creation.

[jadeeeeeeeee]

Hello, while we are still working on the release, users are still able to preview the plugin by building a package from the development branch. The current state of development does have 1.16.4 integrated, so if you would like to try it out, the plugin should function. All you have to do is clone this repo, run it in Unity, and use Create Package in the Tools tab. Let us know if you have any problems with the package creation.

Okay, I'll give it a try. Can Unity version 2021.3.36f1 run it.

[jadeeeeeeeee]

Hello, while we are still working on the release, users are still able to preview the plugin by building a package from the development branch. The current state of development does have 1.16.4 integrated, so if you would like to try it out, the plugin should function. All you have to do is clone this repo, run it in Unity, and use Create Package in the Tools tab. Let us know if you have any problems with the package creation.

I just used Create Package, and it seems that this android eos-sdk.aar was not exported successfully, only 1KB

How about you provide me with a preview version, mainly for Android login and payment functions. Thank you very,much~
My email, [email protected]

[WispyMouse]

@jadeeeeeeeee Were there any Debug Logs that were generated while trying to use the Create Package button? If it failed to export, there might be relevant information there.

[jadeeeeeeeee]

@jadeeeeeeeee Were there any Debug Logs that were generated while trying to use the Create Package button? If it failed to export, there might be relevant information there.

I didn't see anything error in unity's log.

[jadeeeeeeeee]

Hi @jadeeeeeeeee, unfortunately that's not something we are able to do. I can tell you that we anticipate that the new release will happen this week - and I will update this thread when and if that estimation changes.

can you release a version that can be used for epic Android payments first~ Thank you very much for your support.

[WispyMouse]

When I generated a UPM Package from Development, my eos-sdk.aar file is 33,295 KB. So 1 KB is definitely not right, let's see if we can get that building correctly.

If I build without a JSON Description Path, it fails to build with an error logged out. You don't have that error, so you probably provided a json file. What json file did you point to? I have mine pointing at "eos_plugin_for_unity/etc/PackageConfigurations/eos_package_description.json".

I'm going to spend some time now trying to reproduce the issue you have, where the .aar file is generated emptily. Something I'm wondering about is if this is somehow a Git LFS issue. There are many files in our code base that are stored in Git LFS, which gives them a few strange quirks for being pulled down. In a command line for your git repository, could you please:

• Clean the project such that you have no local changes
• run git lfs fetch --all
• Try packaging again

If that still produces a 1KB file, could you please share the contents of that file?

[jadeeeeeeeee]

When I generated a UPM Package from Development, my eos-sdk.aar file is 33,295 KB. So 1 KB is definitely not right, let's see if we can get that building correctly.

If I build without a JSON Description Path, it fails to build with an error logged out. You don't have that error, so you probably provided a json file. What json file did you point to? I have mine pointing at "eos_plugin_for_unity/etc/PackageConfigurations/eos_package_description.json".

I'm going to spend some time now trying to reproduce the issue you have, where the .aar file is generated emptily. Something I'm wondering about is if this is somehow a Git LFS issue. There are many files in our code base that are stored in Git LFS, which gives them a few strange quirks for being pulled down. In a command line for your git repository, could you please:

• Clean the project such that you have no local changes
• run git lfs fetch --all
• Try packaging again

If that still produces a 1KB file, could you please share the contents of that file?

android eos-sdk.aar：
Android.zip

run git lfs fetch --all

Is it possible that I am in China and some networks are blocked.

[WispyMouse]

Looking at the zip, I can definitely tell you have a "git lfs issue". Here's the contents of the dynamic-stdc++\aar\eos-sdk.aar file:

version https://git-lfs.github.com/spec/v1
oid sha256:141f363b32a98fb7174867571f2bd0c073ad0ca3b33909c8fc15e956995db753
size 33796112

This is an indication that when you downloaded the repository, you didn't get the git lfs parts. It's a confusing process for sure! The command line console you have suggests that you didn't download it using git, you may have just downloaded directly from the repository. That's probably because you were instructed to download from the development branch, and don't have an associated release to pull from. I'm willing to bet that there are other problems that are similar, where you have files that aren't properly downloaded from the zip file function.

Are you comfortable using Git enough to pull down the development branch through a git client, and then use that? It should initialize git lfs and function as desired. Otherwise, I requested that my team change the repository in a way that will allow you to download Git LFS items from the Zip archive download. I'll reply to this post when that happens.

[WispyMouse]

Unfortunately upon review with the team, we can't use the setting to enable the Zip archive download to have Git LFS files.

Do you require guidance on using Git to pull down the repository, targeting development?

[jadeeeeeeeee]

yes, I downloaded the dev branch directly.

[jadeeeeeeeee]

I used the corresponding OfferId to initiate the payment, but it prompted me with 'Page Not Found'

C#
CheckoutEntry checkoutEntry = new CheckoutEntry();
checkoutEntry.OfferId = "98316485866d41238d8************";

    Debug.LogError("OfferId:" + checkoutEntry.OfferId);
    CheckoutOptions checkoutOptions = new CheckoutOptions();
    checkoutOptions.LocalUserId = EOSManager.Instance.GetLocalUserId();
    Debug.LogError("LocalUserId:" + checkoutOptions.LocalUserId?.ToString());
    checkoutOptions.Entries = new CheckoutEntry[] { checkoutEntry };

    EOSManager.Instance.GetEOSEcomInterface().Checkout(ref checkoutOptions, "", OnCheckout);

[arthur740212]

Yes, they should be copied over during build.
As for the page not found issue, let us do some investigation, and we'll come back to you.

[joetaylor1987]

@jadeeeeeeeee what did you do to get the Android build working?

[arthur740212]

Hello, it seems that the overlay current only works on landscape mode.
Could you try that out?

[jadeeeeeeeee]

@jadeeeeeeeee what did you do to get the Android build working?

I manually copied these files into the project ,and modified the eos_loginprotocol_stcheme parameter

[jadeeeeeeeee]

Hello, it seems that the overlay current only works on landscape mode. Could you try that out?

After set game on landscape mode, it can indeed work normally!

[jadeeeeeeeee]

I can login and payment normally, but this request “QueryEntitlements” prompts that I have been rejected?

log：

[WispyMouse]

Is this still an issue? Or have you managed to get your entitlements? If not, we can start working on this together.

[jadeeeeeeeee]

I would like to request 'Direct Ownership Enumeration' through our server.
May I ask what this parameter “identityId” is ? and how can I obtain it? Is it an AccessToken?

[joetaylor1987]

@jadeeeeeeeee what did you do to get the Android build working?

I manually copied these files into the project ,and modified the eos_loginprotocol_stcheme parameter

With this I get an error when building - did you include build.gradle, inside eos_dependencies.androidlib?

eos_dependencies.androidlib\build.gradle': 15: Unexpected input: '{' @ line 15, column 9. android {

[jadeeeeeeeee]

I can login and payment normally, but this request “QueryEntitlements” prompts that I have been rejected?

log：

Can you help me take a look at this issue~~~
log：
[WARNING:spdy_session.cc(2975)] Received HEADERS for invalid stream 67

11/27/2024 14:34:38 LogEOS(Warning): Error response received from backend. ServiceName=[Ecommerce], OperationName=[GetV2Entitlements], Url=[], HttpStatus=[403], ErrorCode=[errors.com.epicgames.forbidden], NumericErrorCode=[1003], ErrorMessage=[Sorry, it appears that your client is missing the required [ecommerce] policy to call this API.], CorrId=[EOS-MicJ8y9DMG2hava3AWs4cQ-jscAFB1I1qr2gS6DXvL8dg]

QueryEntitlements callback. ResultCode=AccessDenied
MainSDK:OnQueryEntitlements(QueryEntitlementsCallbackInfo&) Epic.OnlineServices.Ecom.EcomInterface:OnQueryEntitlementsCallbackInternalImplementation(QueryEntitlementsCallbackInfoInternal&)
Epic.OnlineServices.Bindings:EOS_Platform_Tick(IntPtr)
PlayEveryWare.EpicOnlineServices.EOSSingleton:Tick()

[jadeeeeeeeee]

I seem to know why the request was rejected, T_T
After adding the checkbox, I can now make normal requests “QueryEntitlements”

[paulhazen]

Hey @jadeeeeeeeee @joetaylor1987 - Just FYI I am going to move this thread to discussions. If any of you have separate issues, please feel free to open new issues so we can focus on each of them in a concentrated manner. Thank you both for your contributions :)

[jadeeeeeeeee]

I found that the uploaded APK package is limited to 960MB or less, which does not match the description.

[andrew-hirata-playeveryware]

I think this might have been a temporary hickup in Epic's system: are you able to try and upload it again?

[jadeeeeeeeee]

I think this might have been a temporary hickup in Epic's system: are you able to try and upload it again?

Last night they provided feedback that it had been fixed~

[jadeeeeeeeee]

@arthur740212

[kenofori]

@jadeeeeeeeee are you using Unity 6?

[jadeeeeeeeee]

@jadeeeeeeeee are you using Unity 6?

Unity 2021.3.36f1

[jadeeeeeeeee]

We have passed the sandbox billing test, but it seems we encountered issues during the real billing test. Is it due to issues in our region?

epic_android_pay_alipayhk_yasuo.mp4

@arthur740212 @joetaylor1987

[jadeeeeeeeee]

Would it be possible to share with us your debug logs? If you want confidentiality in it, you can email it to our private email alias at [email protected]. Please define ENABLE_DEBUG_EOSMANAGER in your compilation symbols, to add to the useful logs that will be produced.

It's okay, I opened a new demo project to test it.
epic_alipay_error_log.txt

[jadeeeeeeeee]

Would it be possible to share with us your debug logs? If you want confidentiality in it, you can email it to our private email alias at [email protected]. Please define ENABLE_DEBUG_EOSMANAGER in your compilation symbols, to add to the useful logs that will be produced.

Do you have any clues regarding this issue.

[WispyMouse]

I don't know that it's related, but I saw this in your logs:

12/10/2024 14:19:14 LogEOS(Warning): Error response received from backend. ServiceName=[Friend], OperationName=[GetBlockList], Url=[], HttpStatus=[403], ErrorCode=[errors.com.epicgames.common.insufficient_scopes], NumericErrorCode=[1056], ErrorMessage=[Insufficient access scopes. Expected: [friends_list]], CorrId=[EOS-yIrulQdCPxusEcychSzcTA-UG7wTbtFmF5PcBKMMAQkFA]

I'm seeing what looks like a payment success, which suggests that the application is notified properly that a purchase has happened.

pay end Checkout ResultCode： EcomPurchaseProcessing
MainSDK:OnCheckout(CheckoutCallbackInfo&)
Epic.OnlineServices.Ecom.EcomInterface:OnCheckoutCallbackInternalImplementation(CheckoutCallbackInfoInternal&)
Epic.OnlineServices.Bindings:EOS_Platform_Tick(IntPtr)
PlayEveryWare.EpicOnlineServices.EOSSingleton:Tick()

Is it possible there's a callback you're supposed to call to close out your ecommerce overlay, and that the ecommerce callback is calling correctly? Just before this message is another log, perhaps from something you're using for displaying overlay:

2024-12-10 14:20:17.796 4596-4596 cr_AwContents com.PGSoul.BOG2.bogxepica2 W WebView.destroy() called while WebView is still attached to window.

[jadeeeeeeeee]

WebView.destroy()

This log is because I manually closed the payment interface at the end of the video.

[WispyMouse]

To make sure the right help is provided for your issue, can you please open a private discussion with Epic? The ability to do so is linked here: https://eoshelp.epicgames.com/s/?language=en_US

From here, I think your issue doesn't relate to the plugin directly. Epic will have more information on how to support you.