src/apns_connection.erl:22: Warning: undefined callback function terminate/3 (behaviour 'gen_statem') about apns4erl HOT 12 CLOSED

@paulo-ferraz-oliveira Thank you so much. I have another issue to be resolved.

#242.

I hope with this issue, that issue is also resolved. I will update both issues accordingly after OTP 19.x upgrade and testing.

from apns4erl.

Sure...I close this issue. Thank you so much for the help.

from apns4erl.

https://erlang.org/doc/man/gen_statem.html was introduced in OTP 19, so that's what the compiler is complaining about. You have to either bump your OTP version or keep apns4erl at a lower version.

from apns4erl.

@paulo-ferraz-oliveira I am on OTP 19.0.7 or apns4erl v2 will not compile.

I did upgrade from OTP 18 -> 19.

• Is it possible that rebar3 compile is referring to OTP 18 instead of 19?

erl
Erlang/OTP 19 [erts-8.0.5] [source] [64-bit] [async-threads:10] [hipe] [kernel-poll:false]

Eshell V8.0.5  (abort with ^G)
1> 

fromrebar.config
{minimum_otp_vsn, "19"}.

from apns4erl.

Sure, sorry, I read "I have a current prod env on OTP 18" and jumped to a conclusion. Lemme check.

from apns4erl.

For your reference:

 which erl
/usr/local/bin/erl

ls -lrt /usr/local/bin/erl
lrwxrwxrwx 1 root root 21 Mar  2 02:00 /usr/local/bin/erl -> ../lib/erlang/bin/erl

ls /usr/local/lib/erlang/
bin  erts-7.2.1  erts-8.0.5  Install  lib  misc  releases  usr

erl
Erlang/OTP 19 [erts-8.0.5] [source] [64-bit] [async-threads:10] [hipe] [kernel-poll:false]

Eshell V8.0.5  (abort with ^G)
1> 

from apns4erl.

I don't get that on 19.3 (don't have 19.0 locally).

from apns4erl.

OK...let me try 19.3

from apns4erl.

According to the doc.s, not having terminate should not affect you much. I'm not sure if the callback became optional only after 19.0 was out (which is possible).

from apns4erl.

This is where it became optional: erlang/otp@913d0b5.

And this points to it having become so in OTP-19.3, as per Git history.

from apns4erl.

@paulo-ferraz-oliveira #242 is still happening.

OTP: 19.3.6
apns4erl: from master

It happens after couple of days of non-use of apns_connection. For eg.

Last push notification sent:

2021-03-02 21:27:36.030 [info] <0.506.0>@my_mod_apns:sendAPNS:290 Success in request. Reason was: 200 with <<"c2ca5csdsc5b0550a74fe799asda96d9049d3502c58fd5e4b27e98ed1b97e49c2d">>

Then after couple of days of non-use of apns_connection:

2021-03-05 15:51:38.055 [error] <0.530.0> CRASH REPORT Process <0.530.0> with 0 neighbours crashed with reason: no function clause matching gun_http2:parse(<<>>, close) line 77
2021-03-05 15:51:38.056 [error] <0.517.0> Supervisor gun_sup had child gun started with {gun,start_link,undefined} at <0.530.0> exit with reason function_clause in context child_terminated

from apns4erl.

@jainygaurav, if the original issue is solved, "Warning: undefined callback", I think we should move the discussion to #242 and not mix that here. What do you say?

from apns4erl.