When I build my game with IL2CPP and Split Application Binary enabled the PlayFabSharedSettings.asset is missing on some devices. Below I attached a logcat from a device that encountered that issue. I'm using unity 2019.3 and PlayFab SDK 2.78(also tried on different Unity version but the problem remain the same)
I have tested my project on unity 2019.3 with PlayFab SDK 2.78 installed but cannot reproduce your issue.
Have you tried to reinstall the PlayFab Extension and SDK?
You can also create this file via the Extension button on Unity:
This asset is generated by the code in MakeSharedSettingsObj.cs:
AssetDatabase.CreateAsset(asset, "Assets/PlayFabSdk/Shared/Public/Resources/PlayFabSharedSettings.asset");
Can you check if this file exists in your project?
HI @SethDu,yes i deleted the SDK and reinstalled it, didn't make a difference tho. I checked, the playfabsharedsetting.asset is present in unity editor, i even deleted it and made a new, but the problem is still there, Like i said only on some devices is happening. Although if i build without split application binary, then the issue is gone
Can you specify the details of those devices? In addition, is the "Login successful" log generated by PlayFab login API?
hi @FranklinChen, is there any way then that i can still use Playfab, because only by Splitting Application Binary i can update the game on Play Store
Answer by DemonKira · Dec 06, 2019 at 01:37 AM
Probably will keep this thread up, until i found a solotion
Hi @DemonKira, we have informed SDK team to investigate this PlayFabSharedSettings.asset missing issue on specific Android device, if you can provide the detailed error log, it may be helpful to narrow down it, thanks
Hi @DemonKira, we got confirmation and suggestion from engineering team:
1. The current Unity SDK does not support 2019.3 yet, have you tried Unity 2019.2 and observe the behavior?
2. We have recently moved to use asmdef files which may change how our binary is stored. Can you test after updating to the next SDK if the Split Application Binary was fixed?
Hi, so i updated the SDK, currently 2.8, but that issue is still not fixed
Okay, I just forwarded your feedback to the team
Answer by FranklinChen · Feb 11, 2020 at 03:28 AM
Hi @DemonKira, we just got the confirmation that our Unity SDK doesn't have support for Split Application Binary yet. If possible, we can try to ensure not interact with the PlayFab SDK until you've downloaded and installed your .OBB file". We can discuss if that workaround is not worked for you.
hi @FranklinChen is there any way that i can still use playfab, because only by Splitting Application Binary it is possible to update the game on Play Store
Right now, we have to try the above suggestion. If that is impossible, please let me know, let's discuss the possible working way to let you moving forward, thanks.
Sorry for late. The message from product team is saying that we don't have solid workaround at this point. If you find any references or related key points to possibly "lazy load" .obb to avoid this similar issue, please let us know. The engineering team is willing to discuss with you, may I ask your pricing tier? Essential or Paid tier? Could you please tell me your titleid?
The tier is Essential and TitleId is E9C4
Answer by virgilio · Mar 25, 2020 at 01:38 AM
'possibly "lazy load" .obb to avoid this similar issue', really?? thats the suggested solution. Come on playfab you can do better than that :(
Hi @virgilio, fully understand this feature may block Android developers to publish their game, our SDK team is trying to contact with Demon to work out the best solution. Welcome to share your thoughts here:)
hello,@FranklinChenCan provide suggested solution now?
I also have same problem when use Split Application Binary
Thanks your support.