Hey Yair,
Looks like they finally released Unity3D 5.2.0p1 on Sep 18th:
https://unity3d.com/unity/qa/patch-releases/5.2.0p1
Including:
- (719252) - Tizen: Fixed crashes on launch of Tizen projects.
- *(none) - Tizen: Fixed Tizen Store certification errors.*
- (none) - Tizen: Implemented an API to retrieve the window handle.
- (none) - Tizen: Improvements to error messages.
Please do let this group know if you manage to get your game into the Tizen
Store!
On Thu, Aug 13, 2015 at 8:57 PM, Carsten Haitzler <ti...@rasterman.com>
wrote:
> On Thu, 13 Aug 2015 19:03:37 -0400 Yair Salomon <yairsalom...@gmail.com>
> said:
>
> > I'm submitting my Unity game to the Tizen store but was rejected because
> of
> > an undocumented api issue, the thing is that I can't figure out what the
> > problem is.
> >
> > It might be a Unity3D issue as I am the first person on attemting to put
> a
> > game using Unity3D.
> >
> >
> > Thanks in advance
> > Yair Salomon
> >
> >
> > PS: I have attached you the rar file you send with the reasons of
> > rejections.d
>
> 3_core_whitelist.txt
>
> that i think (i don't know how the store does its stuff) is listing "bad
> apis".
>
> first _s_Skin* seem to be api's not from tizen at all... they seem to be
> unresolved symbols to something unity (3d model) related. that smells bad.
> where do these come from? surely not tizen.
>
> but it's the others that are not permitted.
>
> ecore_evas_window_get() almost definitely is not as this exposes display
> system
> specific stuff (window id) which basically says - you're relying on display
> system which we will change in future (x11 -> wayland) ...
>
> app_exit seems to have been a wonderful api break from 2.2 to 2.3. it's now
> ui_app_exit(). tho native c apps were not allowed in 2.2 ... so it shouldnt
> have affected anyone.
>
> then we have ecore_evas_ecore_evas_get() which does mean something is
> playing
> with the lower level api's below the higher level elm porting layer... and
> ecore_imf_* too - to do input method handling - that is not listed as an
> "allowed" api.
>
> so the problem is likely the unity engine tizen port itself is using these
> ...
> and thus you are being pinged for it. this likely needs to be fixed in the
> unity tizen port. what i'm surprised at here is that there was no actual
> check
> of this BEFORE announcing tizen support in unity and then having developers
> depend on it.
>
> so this is something where unity devs (and tizen devs) need to talk and
> work
> this out. some are simply changes for unity devs to move to, others may
> require
> rewriting a whole blob of code (ecore_imf and ecore_evas api usages) and
> finding the mysterious _s_Skin ... api references.
>
> --
> Carsten Haitzler (The Rasterman) <ti...@rasterman.com>
> _______________________________________________
> Application-dev mailing list
> Application-dev@lists.tizen.org
> https://lists.tizen.org/listinfo/application-dev
>
--
b...@summerwill.net
_______________________________________________
Application-dev mailing list
Application-dev@lists.tizen.org
https://lists.tizen.org/listinfo/application-dev
